create_backup_plan · Storage MCP: Risk & Policy

WHAT IT DOES

What create_backup_plan does on Storage

AI agents use create_backup_plan to create or update resources in Storage — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Storage environment.

WHY IT NEEDS A POLICY

Why create_backup_plan needs a policy

This tool creates a new backup plan configuration, which is a reversible write operation. It modifies the backup infrastructure but does not execute arbitrary code, move funds, or irreversibly delete data. The severity is medium because misconfiguration of backup plans could impact data protection posture, but the operation itself is not destructive and can be modified or deleted later.

From the tool's definition Tool name 'create_backup_plan' and description 'Creates a new backup plan' indicate creation of a new resource/configuration in Google Cloud Storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_backup_plan Rate-limited

create_backup_plan stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_backup_plan": {
      "limits": [
        {
          "counter": "create_backup_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Storage, so you can run agents against it safely.

FAQ

Questions about create_backup_plan

What does the create_backup_plan tool do? +

Creates a new backup plan. It is categorised as a Write tool in the Storage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_backup_plan? +

Register the Storage MCP server in PolicyLayer and add a rule for create_backup_plan: 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 Storage. Nothing to install.

What risk level is create_backup_plan? +

create_backup_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_backup_plan? +

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

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

create_backup_plan is provided by the Storage MCP server (@google-cloud/storage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.