cancel_backups

Cancel backups for a Linode instance

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/cancel-backups.md

WHAT IT DOES

What cancel_backups does on Linode MCP Server

AI agents call cancel_backups 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.

RISK

Why cancel_backups is rated Critical

This tool irreversibly removes backup data for an instance, which cannot be recovered once cancelled. While it doesn't directly delete instance data, it destroys the recovery mechanism—a critical safety net. The blast radius includes potential data loss if the instance fails after backups are cancelled.

From the tool's definition cancel_backups cancels backups for a Linode instance. Cancellation of backups is an irreversible action that removes the ability to restore from those backups, destroying backup data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_backups 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_backups, this is the rule to start with:

cancel_backups Hidden

cancel_backups is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_backups"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every cancel_backups call is checked against it from then on.

FAQ

Questions about cancel_backups

What does the cancel_backups tool do? +

Cancel backups for a Linode 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.

How do I enforce a policy on cancel_backups? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for cancel_backups: 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.

What risk level is cancel_backups? +

cancel_backups is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_backups? +

Yes. Add a rate_limit block to the cancel_backups 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.

How do I block cancel_backups completely? +

Set action: deny in the PolicyLayer policy for cancel_backups. 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.

What MCP server provides cancel_backups? +

cancel_backups 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.

KEEP EXPLORING

More on Linode MCP Server, and thousands of servers like it.

This server

All 416 Linode MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →