AI agents call gcloud_list_jobs 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 performs a read-only query operation that retrieves and displays information about Cloud Run Jobs (name, status, counts, timestamps). It has no side effects, does not create, modify, or delete resources, and does not execute any jobs or code. It falls clearly into the Read category with low severity since it only exposes already-accessible metadata about job configurations and history.
From the tool's definition Tool name 'gcloud_list_jobs' and description 'List Cloud Run Jobs in a region. Shows job name, last execution status, execution count, and creation time.' indicate retrieval of existing job metadata with no modification or execution.
Attacks that exploit this kind of access
List Cloud Run Jobs in a region. Shows job name, last execution status, execution count, and creation time. 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_list_jobs: 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_list_jobs 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_list_jobs 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_list_jobs. 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_list_jobs 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 →