List all request naming rules (classic Config API v1).
AI agents call list_request_namings 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.
The tool queries and retrieves existing request naming rule configurations from Dynatrace without creating, modifying, deleting, or executing anything. It is a passive read operation on observability configuration data. Severity is low because listing naming rules poses minimal risk—the data returned is metadata about how requests are categorized, not sensitive operational secrets or financial information.
From the tool's definition Tool name 'list_request_namings' uses the verb 'list', and description states 'List all request naming rules'. This is a retrieval operation with no modification or execution side effects.
Attacks that exploit this kind of access
List all request naming rules (classic Config API 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 list_request_namings: 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.
list_request_namings 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 list_request_namings 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 list_request_namings. 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.
list_request_namings 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 →