trigger_backup · Storage MCP: Risk & Policy

WHAT IT DOES

What trigger_backup does on Storage

AI agents invoke trigger_backup to trigger actions in Storage. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why trigger_backup needs a policy

This tool initiates a backup process—an operation that runs external procedures against cloud storage infrastructure. While backups are generally protective rather than destructive, the action is irreversible once triggered and could consume significant resources, trigger data transfers, or create snapshots that cannot be undone instantly.

From the tool's definition Tool name 'trigger_backup' and description 'Triggers a backup for a given backup plan association' indicate the tool executes a backup operation, which is an external operation whose effects depend on arguments (which backup plan association to target).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_backup Rate-limited

trigger_backup stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_backup": {
      "limits": [
        {
          "counter": "trigger_backup_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 trigger_backup

What does the trigger_backup tool do? +

Triggers a backup for a given backup plan association. It is categorised as a Execute tool in the Storage MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_backup? +

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

What risk level is trigger_backup? +

trigger_backup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit trigger_backup? +

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

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

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