Test parsing tabular lookup data (Grail Resource Store v1) WITHOUT storing anything.
AI agents call test_lookup_pattern 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 validation and parsing of tabular lookup data without side effects—no data is created, modified, deleted, or stored. It is purely diagnostic/read-only in nature. The low severity reflects minimal blast radius: misuse would at worst return parse errors or expose data schema patterns, not corrupt or delete data.
From the tool's definition Tool description explicitly states 'WITHOUT storing anything' and 'Test parsing' indicates a read-only validation operation on lookup data structure.
Attacks that exploit this kind of access
Test parsing tabular lookup data (Grail Resource Store v1) WITHOUT storing anything. 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 test_lookup_pattern: 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.
test_lookup_pattern 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 test_lookup_pattern 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 test_lookup_pattern. 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.
test_lookup_pattern 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 →