AI agents call get_object_metadata to retrieve information from Gcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata information about a Cloud Storage object, which is a read-only operation with no side effects. It does not modify, delete, or execute any code. The blast radius of misuse is minimal—an attacker could only gain visibility into object metadata properties, not access the actual object content or make changes.
From the tool's definition Tool name 'get_object_metadata' and description 'Return metadata for a single Cloud Storage object' indicate retrieval of object metadata without modification or deletion.
Attacks that exploit this kind of access
Return metadata for a single Cloud Storage object. It is categorised as a Read tool in the Gcp MCP Server, which means it retrieves data without modifying state.
Register the Gcp MCP server in PolicyLayer and add a rule for get_object_metadata: 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. Nothing to install.
get_object_metadata 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_object_metadata 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_object_metadata. 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_object_metadata is provided by the Gcp MCP server (lokimcpuniverse/gcp-mcp-server). 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 →