Set lifecycle rules for a Cloud Storage bucket
AI agents use storage_set_bucket_lifecycle 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.
This is a Write operation because it creates or modifies bucket lifecycle policies, which are reversible configuration settings. While lifecycle rules can eventually cause data deletion through automation, the tool itself only sets the rules—it does not directly delete data.
From the tool's definition The tool name 'storage_set_bucket_lifecycle' and description 'Set lifecycle rules for a Cloud Storage bucket' indicate modification of bucket configuration.
Attacks that exploit this kind of access
Set lifecycle rules 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.
Register the Google Cloud MCP server in PolicyLayer and add a rule for storage_set_bucket_lifecycle: 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.
storage_set_bucket_lifecycle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the storage_set_bucket_lifecycle 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.
Set action: deny in the PolicyLayer policy for storage_set_bucket_lifecycle. 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.
storage_set_bucket_lifecycle 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →