AI agents call blob_exists 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 performs a simple existence check on a blob in Google Cloud Storage, which is a read-only operation with no side effects. It retrieves information without altering state, making it categorically a Read operation. The severity is low because an AI agent misusing this tool would merely check for blob existence across the storage bucket, causing no data loss, financial impact, or operational disruption.
From the tool's definition Tool name 'blob_exists' and description 'Check if a blob exists' indicate a query operation that only retrieves existence status without modifying, deleting, or executing code.
Documented attack patterns abuse exactly the kind of access blob_exists 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 blob_exists:
{
"version": "1",
"default": "deny",
"tools": {
"blob_exists": {}
}
}blob_exists 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.
Check if a blob exists. 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 blob_exists: 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.
blob_exists 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 blob_exists 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 blob_exists. 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.
blob_exists 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.