cancel_object_storage
Cancel Object Storage service
This record as markdown: /tools/takashito-linode-mcp-server/cancel-object-storage.md
What cancel_object_storage does on Linode MCP Server
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.
Why cancel_object_storage is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs cancel_object_storage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_object_storage, this is the rule to start with:
cancel_object_storage is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every cancel_object_storage call is checked against it from then on.
Questions about cancel_object_storage
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.
More on Linode MCP Server, and thousands of servers like it.
Across the catalogue