delete_fieldset

Delete a Grail fieldset by UID (WRITE, Storage Fieldsets v1).

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

What delete_fieldset does on Dynatrace SaaS MCP Server

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

Deletion of a fieldset is an irreversible operation that destroys data configuration. Even though the API spec labels it WRITE, the actual effect is permanent removal of a storage structure, which cannot be undone without restore/backup. This qualifies as Destructive per the rules: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.

From the tool's definition Tool name explicitly contains 'delete'; description states 'Delete a Grail fieldset by UID'. The API classification '(WRITE, Storage Fieldsets v1)' is contradictory but the action itself is irreversible deletion.

Questions about delete_fieldset

What does the delete_fieldset tool do? +

Delete a Grail fieldset by UID (WRITE, Storage Fieldsets 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_fieldset? +

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

delete_fieldset 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_fieldset? +

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

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

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