get_record_deletion_status

Get the status of a previously submitted Grail record deletion process.

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

What get_record_deletion_status does on Dynatrace SaaS MCP Server

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

This tool only retrieves status information about a deletion process that was already submitted. It performs no creation, modification, execution, or destruction of data—it simply reads the state of an existing async operation. This is a classic Read operation with minimal security impact.

From the tool's definition Tool name 'get_record_deletion_status' and description 'Get the status of a previously submitted Grail record deletion process' indicate a retrieval operation that queries the status of an existing deletion request without modifying or executing anything.

Questions about get_record_deletion_status

What does the get_record_deletion_status tool do? +

Get the status of a previously submitted Grail record deletion process. 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_record_deletion_status? +

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

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

Can I rate-limit get_record_deletion_status? +

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

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

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