AI agents call gcloud_get_job_execution to retrieve information from Gcloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves execution metadata and status information from Cloud Run Jobs without modifying, creating, or deleting any resources. It is a straightforward query operation that returns job execution details for inspection purposes. Even if the logs URI is included, the tool itself only retrieves a reference, not executing or modifying anything.
From the tool's definition Tool name and description indicate retrieval only: 'Get Cloud Run Job execution details including task counts, status, timing, and log URI.' The verb 'Get' and the enumeration of read-only fields (counts, status, timing, URIs) confirm no data modification or…
Attacks that exploit this kind of access
Get Cloud Run Job execution details including task counts, status, timing, and log URI. It is categorised as a Read tool in the Gcloud MCP Server, which means it retrieves data without modifying state.
Register the Gcloud MCP server in PolicyLayer and add a rule for gcloud_get_job_execution: 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 Gcloud. Nothing to install.
gcloud_get_job_execution 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 gcloud_get_job_execution 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 gcloud_get_job_execution. 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.
gcloud_get_job_execution is provided by the Gcloud MCP server (prmichaelsen/gcloud-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 →