Get detailed information about a Cloud Storage bucket
AI agents call storage_get_bucket_info to retrieve information from Google Cloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns bucket metadata (configuration, settings, attributes) but does not create, modify, delete, or execute operations. It is a pure information retrieval operation with no blast radius beyond potential exposure of bucket configuration details. Classified as Read with low severity.
From the tool's definition Tool name contains 'get' and description states 'Get detailed information about a Cloud Storage bucket' — classic read operation that retrieves metadata without modification or side effects.
Attacks that exploit this kind of access
Get detailed information about a Cloud Storage bucket. It is categorised as a Read tool in the Google Cloud MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud MCP server in PolicyLayer and add a rule for storage_get_bucket_info: 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_get_bucket_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the storage_get_bucket_info 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_get_bucket_info. 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_get_bucket_info 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 →