Low Risk

get_backup

Get details for a specific backup

How to control get_backup ↓

What get_backup does on Linode MCP Server

AI agents call get_backup to retrieve information from Linode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_backup needs a policy

This tool retrieves information about a backup without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query operation with minimal risk—backup metadata retrieval cannot cause infrastructure changes or data loss.

From the tool's definition Tool name 'get_backup' and description 'Get details for a specific backup' indicate a retrieval operation with no side effects. The verb 'get' and 'details' confirm data querying without modification or deletion.

Documented attack patterns abuse exactly the kind of access get_backup gives an agent:

How to control get_backup

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 get_backup:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_backup": {}
  }
}

get_backup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Linode MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_backup

What does the get_backup tool do? +

Get details for a specific backup. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_backup? +

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

get_backup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_backup? +

Yes. Add a rate_limit block to the get_backup 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 get_backup completely? +

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

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

Enforce policy on every Linode MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.