AI agents call get_bucket_info to retrieve information from Gcp Storage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about a GCS bucket without creating, modifying, or deleting any data. It is a read-only query operation with minimal blast radius if misused by an AI agent—the worst outcome would be information disclosure of bucket properties that are often already accessible to authenticated users.
From the tool's definition Tool name 'get_bucket_info' and description 'Get detailed information about a bucket' indicate a retrieval operation with no modification, deletion, or execution of external code.
Documented attack patterns abuse exactly the kind of access get_bucket_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gcp Storage, and nothing reaches the server without passing your rules. This is the rule we recommend for get_bucket_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_bucket_info": {}
}
}get_bucket_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a bucket. It is categorised as a Read tool in the Gcp Storage MCP Server, which means it retrieves data without modifying state.
Register the Gcp Storage MCP server in PolicyLayer and add a rule for 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 Gcp Storage. Nothing to install.
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 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 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.
get_bucket_info is provided by the Gcp Storage MCP server (uysalserkan/gcp-storage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gcp Storage, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Gcp Storage tools catalogued and risk-classified — across an index of 43,000+ MCP servers.