list_request_attributes

List all request attribute definitions (classic Config API v1).

Server Dynatrace SaaS MCP Server mnmozi/dynatrace-mcp-saas
Category Read
Risk class Low
Parameters 00 required

What list_request_attributes does on Dynatrace SaaS MCP Server

AI agents call list_request_attributes 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.

Why list_request_attributes needs a policy

This tool queries and retrieves existing request attribute definitions from Dynatrace without creating, modifying, deleting, or executing anything. Listing configuration metadata poses minimal risk—it exposes schema/structure information that is typically non-sensitive or already known to legitimate operators. An LLM agent misusing this tool would only retrieve data, not cause damage.

From the tool's definition Tool name 'list_request_attributes' and description 'List all request attribute definitions' indicate a retrieval operation with no side effects. The verb 'list' is a canonical Read action.

Questions about list_request_attributes

What does the list_request_attributes tool do? +

List all request attribute definitions (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.

How do I enforce a policy on list_request_attributes? +

Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for list_request_attributes: 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.

What risk level is list_request_attributes? +

list_request_attributes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_request_attributes? +

Yes. Add a rate_limit block to the list_request_attributes 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.

How do I block list_request_attributes completely? +

Set action: deny in the PolicyLayer policy for list_request_attributes. 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.

What MCP server provides list_request_attributes? +

list_request_attributes 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.