AI agents call cancel_object_storage 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.
Canceling an Object Storage service is an irreversible action that terminates service and access to stored data. While not a direct deletion command, service cancellation is a destructive operation comparable to dropping a database or removing infrastructure. This warrants the Destructive category rather than Execute because the primary effect is termination/removal rather than conditional execution.
From the tool's definition cancel_object_storage: Cancel Object Storage service. The verb 'cancel' indicates termination of a service, which is an irreversible action that removes access to and potentially results in data loss of stored objects.
Documented attack patterns abuse exactly the kind of access cancel_object_storage 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 cancel_object_storage:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_object_storage"
]
}cancel_object_storage 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.
Cancel Object Storage service. 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 cancel_object_storage: 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.
cancel_object_storage 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 cancel_object_storage 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 cancel_object_storage. 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.
cancel_object_storage 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.