create_backup_vault · Storage MCP: Risk & Policy

WHAT IT DOES

What create_backup_vault does on Storage

AI agents use create_backup_vault 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_vault needs a policy

This tool creates a new backup vault, which is a reversible Write operation that modifies the storage infrastructure by adding a new resource. It does not execute arbitrary code, delete data, or move money. The medium severity reflects that misconfiguration could affect backup strategy and storage organization, but the action itself is non-destructive and can be reversed or modified later.

From the tool's definition Tool name 'create_backup_vault' and description 'Creates a new backup vault' indicate creation of a new resource in GCS storage infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_backup_vault Rate-limited

create_backup_vault 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_vault": {
      "limits": [
        {
          "counter": "create_backup_vault_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_vault

What does the create_backup_vault tool do? +

Creates a new backup vault. 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_vault? +

Register the Storage MCP server in PolicyLayer and add a rule for create_backup_vault: 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_vault? +

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

Can I rate-limit create_backup_vault? +

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

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

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