New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_alert_definition

Delete an alert definition

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/delete-alert-definition.md

What delete_alert_definition does on Linode MCP Server

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

Why delete_alert_definition is rated Critical

Deletion of alert definitions is a destructive action that cannot be undone. Once deleted, the alert definition is permanently removed and any monitoring/alerting rules it contained are lost. This falls under the Destructive category (more severe than Write) because the operation is irreversible.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete an alert definition' - this is an irreversible deletion operation that removes a configuration object.

Questions about delete_alert_definition

What does the delete_alert_definition tool do? +

Delete an alert definition. It is categorised as a Destructive tool in the Linode 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_alert_definition? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for delete_alert_definition: 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 Linode MCP Server. Nothing to install.

What risk level is delete_alert_definition? +

delete_alert_definition 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_alert_definition? +

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

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

delete_alert_definition is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Linode MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Linode MCP Server's. Pull the full record:

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.