// SCAN REPORT

Storage

61 tools. 24 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated: 26 Jun 2026

24 can modify or destroy data

37 read-only

61 tools total

Community server · catalogue entry verified 26/06/2026

How to control Storage ↓

TOOL MAP

What Storage exposes to your agents

Read (37) Write / Execute (17) Destructive / Financial (7)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Storage tools

Destructive · High delete_backup This tool irreversibly removes backup data from GCS storage. Destructive · High delete_backup_plan This tool performs an irreversible deletion of a backup plan, which fits the Destructive category definition. Destructive · High delete_backup_plan_association Deletion of backup plan associations is irreversible and cannot be undone through normal means. Destructive · High delete_backup_vault This tool performs an irreversible deletion operation on backup vault infrastructure.

24 of Storage's 61 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Storage

PolicyLayer is an MCP gateway — it sits between your AI agents and Storage, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_backup": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "copy_object": {
    "limits": [
      {
        "counter": "copy_object_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_iam_permissions": {
    "limits": [
      {
        "counter": "check_iam_permissions_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Storage — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON STORAGE →

Instant setup, no code required.

FULL CATALOGUE

All 61 Storage tools

DESTRUCTIVE 7 tools

Destructive delete_backup Deletes a backup. Destructive delete_backup_plan Deletes a backup plan. Destructive delete_backup_plan_association Deletes a backup plan association. Destructive delete_backup_vault Deletes a backup vault. Destructive delete_bucket Deletes a bucket. Destructive delete_object Deletes a specific object. Destructive move_object Moves an object from one bucket to another or renames it within the same bucket by copying and deleting the or

EXECUTE 2 tools

Execute execute_insights_query Executes a BigQuery SQL query against an insights dataset and returns the result. Execute trigger_backup Triggers a backup for a given backup plan association.

WRITE 15 tools

Write copy_object Copies an object from one bucket to another or within the same bucket. Write copy_object_safe Copies an object to a new destination. Fails if an object already exists at the destination. Write create_backup_plan Creates a new backup plan. Write create_backup_plan_association Creates a new backup plan association. Write create_backup_vault Creates a new backup vault. Write create_bucket Creates a new bucket with specified configuration. Write csql_restore Restores a Cloud SQL backup to a Cloud SQL instance. Write restore_backup Restores a Backup resource to a target environment. Supports Compute Instances and Disks. Write update_backup_plan Updates a backup plan. Write update_bucket_labels Updates labels for a bucket. Write update_object_metadata Updates the metadata of an existing object. Write upload_object Uploads a file to a GCS bucket. Write upload_object_safe Uploads a file to a GCS bucket. Fails if the object already exists. Write write_object Writes a new object to the bucket. Write write_object_safe Writes a new object to the bucket. Fails if the object already exists.

READ 37 tools

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Storage

Can an AI agent delete data through the Storage MCP server? +

Yes. The Storage server exposes 7 destructive tools including delete_backup, delete_backup_plan, delete_backup_plan_association. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Storage? +

The Storage server has 15 write tools including copy_object, copy_object_safe, create_backup_plan. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Storage.

How many tools does the Storage MCP server expose? +

61 tools across 4 categories: Destructive, Execute, Read, Write. 37 are read-only. 24 can modify, create, or delete data.

How do I enforce a policy on Storage? +

Register the Storage MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Storage tool call.

Deterministic rules across all 61 Storage tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON STORAGE →

Instant setup, no code required.

61 Storage tools catalogued and risk-classified — across an index of 43,000+ MCP servers.