Fetch all spans for a single trace id (ordered by start time) for latency/root-cause analysis.
AI agents call get_trace 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 trace span data from Dynatrace for analysis purposes. It has no side effects, does not modify or delete data, and does not execute arbitrary operations. The blast radius of misuse is minimal—an agent could retrieve trace data it shouldn't access (information disclosure risk), but this is an access control concern rather than a tool capability concern. It is clearly a Read operation.
From the tool's definition Tool name is 'get_trace' and description states 'Fetch all spans for a single trace id' — the verb 'Fetch' indicates data retrieval with no modification or deletion. The stated purpose is 'latency/root-cause analysis', a read-only observability operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Fetch all spans for a single trace id (ordered by start time) for latency/root-cause analysis. 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 get_trace: 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.
get_trace 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 get_trace 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 get_trace. 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.
get_trace 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 →