storage_enable_versioning · Google Cloud MCP: Risk & Policy

WHAT IT DOES

What storage_enable_versioning does on Google Cloud

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

WHY IT NEEDS A POLICY

Why storage_enable_versioning needs a policy

This tool modifies Cloud Storage bucket metadata/configuration by toggling versioning. It is reversible (versioning can be toggled back on or off), so it falls under Write rather than Destructive. However, disabling versioning could have consequences for data recovery.

From the tool's definition Tool description states 'Enable or disable versioning for a Cloud Storage bucket' - this modifies bucket configuration settings that can be reversed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

storage_enable_versioning Rate-limited

storage_enable_versioning 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": {
    "storage_enable_versioning": {
      "limits": [
        {
          "counter": "storage_enable_versioning_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 Google Cloud, so you can run agents against it safely.

FAQ

Questions about storage_enable_versioning

What does the storage_enable_versioning tool do? +

Enable or disable versioning for a Cloud Storage bucket. It is categorised as a Write tool in the Google Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on storage_enable_versioning? +

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

What risk level is storage_enable_versioning? +

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

Can I rate-limit storage_enable_versioning? +

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

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

storage_enable_versioning is provided by the Google Cloud MCP server (lockon-n/google-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

storage_enable_versioning is one line of Google Cloud's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →