Evaluate an SLO by ID and return its compliance result (platform SLO v1).
AI agents call evaluate_slo 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 retrieves observability data (SLO compliance metrics) based on an identifier. It performs no data modification, deletion, code execution, or external operation triggering. The action is a read-only query of existing SLO evaluation results, making it a Read category tool with low severity.
From the tool's definition Tool name 'evaluate_slo' and description 'Evaluate an SLO by ID and return its compliance result' indicates a query operation that retrieves and returns SLO compliance data without modifying or triggering external actions.
Attacks that exploit this kind of access
Evaluate an SLO by ID and return its compliance result (platform SLO v1). 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 evaluate_slo: 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.
evaluate_slo 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 evaluate_slo 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 evaluate_slo. 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.
evaluate_slo 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 →