Queries a single Smartscape entity by id via Grail DQL (Gen3-native).
AI agents call get_entity 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 from Dynatrace's Smartscape by entity ID. It performs a read-only query operation with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an agent could retrieve sensitive observability details, but cannot modify systems or trigger actions.
From the tool's definition Tool name 'get_entity' and description 'Queries a single Smartscape entity by id' indicate a retrieval operation. The use of 'Queries' confirms data retrieval without modification or deletion.
Attacks that exploit this kind of access
Queries a single Smartscape entity by id via Grail DQL (Gen3-native). 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_entity: 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_entity 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_entity 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_entity. 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_entity 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 →