delete_request_attribute

Delete a request attribute by ID (WRITE, destructive, classic Config API v1).

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

What delete_request_attribute does on Dynatrace SaaS MCP Server

AI agents call delete_request_attribute to permanently remove resources in Dynatrace SaaS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_request_attribute needs a policy

This tool permanently removes a request attribute configuration from Dynatrace. Deletion is irreversible and constitutes a destructive action that could break observability pipelines and monitoring rules that depend on the deleted attribute. The explicit "destructive" label in the description confirms this categorization.

From the tool's definition Tool description explicitly states "Delete a request attribute by ID" and is marked "destructive" in the description. Request attributes are configuration entities in Dynatrace that cannot be recovered once deleted.

Questions about delete_request_attribute

What does the delete_request_attribute tool do? +

Delete a request attribute by ID (WRITE, destructive, classic Config API v1). It is categorised as a Destructive tool in the Dynatrace SaaS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_request_attribute? +

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

delete_request_attribute is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_request_attribute? +

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

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

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