AI agents call delete_resource_lock 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.
Deleting a resource lock removes a safeguard that prevents accidental or malicious modification/deletion of infrastructure resources. While not directly destructive to data, removing locks enables subsequent destructive actions and cannot be undone without manual re-creation.
From the tool's definition Tool name is 'delete_resource_lock' with description 'Delete a resource lock'. The verb 'delete' combined with 'resource lock' indicates irreversible removal of a protective mechanism.
Documented attack patterns abuse exactly the kind of access delete_resource_lock 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_resource_lock:
{
"version": "1",
"default": "deny",
"hide": [
"delete_resource_lock"
]
}delete_resource_lock 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 a resource lock. 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_resource_lock: 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_resource_lock 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_resource_lock 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_resource_lock. 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_resource_lock 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.