delete_instance
AI agents call delete_instance 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.
delete_instance removes cloud computing instances—a permanent, non-reversible action. An AI agent misuse could terminate production workloads, causing significant downtime and data loss. This qualifies as Destructive (most severe applicable category), not merely Execute, because the effect cannot be undone and the blast radius is infrastructure-wide.
From the tool's definition Tool name 'delete_instance' combined with server description that explicitly mentions 'deleting Linode instances' indicates irreversible deletion of cloud infrastructure resources.
Attacks that exploit this kind of access
delete_instance. 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_instance: 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_instance 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_instance 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_instance. 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_instance is provided by the Linode MCP Server MCP server (komer3/linode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →