get_request_attribute

Get a single request attribute definition by ID (classic Config API v1).

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

What get_request_attribute does on Dynatrace SaaS MCP Server

AI agents call get_request_attribute 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 get_request_attribute needs a policy

This tool retrieves metadata about a request attribute definition from Dynatrace configuration. It performs a read-only query operation that returns observability configuration data without creating, modifying, deleting, or executing any changes. The blast radius of misuse is minimal—an agent could only retrieve attribute definitions that already exist, with no ability to alter system state.

From the tool's definition Tool name 'get_request_attribute' and description 'Get a single request attribute definition by ID' indicate a retrieval operation with no modification or side effects.

Questions about get_request_attribute

What does the get_request_attribute tool do? +

Get a single request attribute definition by ID (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 get_request_attribute? +

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

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

Can I rate-limit get_request_attribute? +

Yes. Add a rate_limit block to the get_request_attribute 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 get_request_attribute completely? +

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

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