Compare committed settings-schema versions against the live tenant.
AI agents call check_settings_schema_drift to retrieve information from Dynatrace SaaS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only comparison between two sets of schema data (committed versions vs. live tenant state). It retrieves information to detect differences but does not create, modify, delete, or execute any changes. The blast radius of misuse is minimal—worst case, an agent obtains visibility into configuration drift, which is non-destructive.
From the tool's definition Tool name 'check_settings_schema_drift' and description 'Compare committed settings-schema versions against the live tenant' indicate a comparison/verification operation.
Attacks that exploit this kind of access
Compare committed settings-schema versions against the live tenant. It is categorised as a Read tool in the Dynatrace SaaS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for check_settings_schema_drift: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Dynatrace SaaS MCP Server. Nothing to install.
check_settings_schema_drift is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_settings_schema_drift rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for check_settings_schema_drift. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
check_settings_schema_drift is provided by the Dynatrace SaaS MCP Server MCP server (mnmozi/dynatrace-mcp-saas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →