Get full details of one problem, including root cause and affected entities.
AI agents call get_problem 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 problem details from Dynatrace observability platform, which is a read-only query operation. It has no side effects on system state, infrastructure, or data integrity. The blast radius of misuse is minimal—an agent could only access observability metadata that should be available to authenticated users. This is consistent with the 'Read' category for data retrieval operations.
From the tool's definition Tool name 'get_problem' and description 'Get full details of one problem, including root cause and affected entities' indicate retrieval of existing observability data with no modification, creation, deletion, or execution of operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get full details of one problem, including root cause and affected entities. 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_problem: 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_problem 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_problem 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_problem. 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_problem 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 →