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.
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.
Documented attack patterns abuse exactly the kind of access delete_alert_definition gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_alert_definition:
{
"version": "1",
"default": "deny",
"hide": [
"delete_alert_definition"
]
}delete_alert_definition disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
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.
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.
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.
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.
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.
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.
Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.