Preferences Deployment Reference

This page is for admins and consultants who operate SemanticOps MCP deployments.

End users should use:

What this page covers

The end-user Preferences pages already document runtime setting IDs (formatting, masking, limits, completion, notifications):

This page covers deployment-level controls that are not regular manage_preferences settings.

Deployment-level controls for formatting

DAX formatting service controls

  • MCP_ENGINE_DAX_FORMATTING_ENABLED
  • MCP_ENGINE_DAX_FORMATTING_ADMIN_DISABLE
  • MCP_ENGINE_DAX_FORMATTING_TIMEOUT_MS
  • MCP_ENGINE_DAX_FORMATTING_LINE_STYLE
  • MCP_ENGINE_DAX_FORMATTING_SPACING_STYLE
  • MCP_ENGINE_DAX_FORMATTING_LIST_SEPARATOR
  • MCP_ENGINE_DAX_FORMATTING_DECIMAL_SEPARATOR

M formatting service controls

  • MCP_ENGINE_M_FORMATTING_ENABLED
  • MCP_ENGINE_M_FORMATTING_ADMIN_DISABLE
  • MCP_ENGINE_M_FORMATTING_TIMEOUT_MS
  • MCP_ENGINE_M_FORMATTING_LINE_WIDTH
  • MCP_ENGINE_M_FORMATTING_INDENT_LENGTH
  • MCP_ENGINE_M_FORMATTING_INDENT_STYLE

Deployment-level controls for masking

PII masking

  • MCP_ENGINE_PII_MASKING
  • MCP_ENGINE_FORCE_DISABLE_PII_MASKING
  • MCP_ENGINE_PII_PATTERNS (custom regex patterns)
  • MCP_ENGINE_PII_DETECTOR_PROFILES
  • MCP_ENGINE_PII_SEMANTIC_PROFILES
  • MCP_ENGINE_PII_AUTO_SEMANTIC_PROFILES_FROM_CULTURE
  • MCP_ENGINE_PII_FREE_TEXT_MODE
  • MCP_ENGINE_PII_EXCLUDE_COLUMNS

Notes:

  • Custom regex patterns are deployment-level; they are not a user-facing manage_preferences setting.
  • Semantic profiles control localized model labels; detector profiles control value patterns.
  • Culture-derived PII semantic profiles are additive by default.
  • Accepted PII detector profiles: us_common, europe_common, latam_common, apac_common, oceania_common.
  • Accepted PII semantic profiles: en_common, de_common, fr_common, es_common, cz_common.
  • Default free-text mode is StructuredAndContextual; use StructuredOnly for structured identifiers only, or WholeValue for stricter whole-field masking.
  • PII table-level exclusions are typically handled through Preferences (pii_masking_exclude_tables) or deployment config.

Numeric masking

  • MCP_ENGINE_NUMERIC_MASKING
  • MCP_ENGINE_FORCE_DISABLE_NUMERIC_MASKING
  • MCP_ENGINE_NUMERIC_MASKING_PROFILES
  • MCP_ENGINE_NUMERIC_AUTO_PROFILES_FROM_CULTURE
  • MCP_ENGINE_NUMERIC_EXCLUDE_COLUMNS
  • MCP_ENGINE_NUMERIC_EXCLUDE_TABLES

Notes:

  • Numeric masking scalar ranges and token dictionaries are deployment config concerns, not manage_preferences setting IDs.
  • Numeric hint profiles control structural/reference-code and ratio labels.
  • Culture-derived numeric profiles are additive by default. To disable built-in and culture-derived numeric profiles together, configure an empty profile list and turn off numeric auto-profiles from culture.
  • Accepted numeric profiles: reference_common, us_common, europe_common, latam_common, apac_common, oceania_common.

Persistence model (server-side)

Runtime settings managed by manage_preferences are stored server-side in the global preferences store.

Model-level masking intent

Separate from deployment config and runtime preferences, SemanticOps MCP also honors model annotations on tables and columns:

  • McpEngine_PiiMasking: force or exclude
  • McpEngine_NumericMasking: force or exclude

These annotations are useful when masking intent should travel with the semantic model instead of being tied only to one server environment.

See also