GET BATCH JOB STATUS - Check status of running batch job with optional auto-polling. STATES: PENDING (queued), RUNNING (processing), SUCCEEDED (complete), FAILED (error), CANCELLED (user stopped), EXPIRED (timeout). WORKFLOW: 1) Call with batch job name/ID, 2) Optionally enable polling to wait fo...
AI agents call batch_get_status to retrieve information from Gemini MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries the status of an existing batch job. It retrieves information about a job's progress and state without modifying, deleting, or executing any operations. The auto-polling feature is passive monitoring, not an active execution. Low severity because status checks have minimal blast radius—an agent cannot cause harm by checking job status.
From the tool's definition Tool description explicitly states 'GET BATCH JOB STATUS' and 'Check status of running batch job'. Returns 'current state, progress stats, and completion info' with no modification or deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
GET BATCH JOB STATUS - Check status of running batch job with optional auto-polling. STATES: PENDING (queued), RUNNING (processing), SUCCEEDED (complete), FAILED (error), CANCELLED (user stopped), EXPIRED (timeout). WORKFLOW: 1) Call with batch job name/ID, 2) Optionally enable polling to wait for completion, 3) Returns current state, progress stats, and completion info. USAGE: Pass job name from batch_create response. Enable autoPoll for hands-off waiting. It is categorised as a Read tool in the Gemini MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gemini MCP Server MCP server in PolicyLayer and add a rule for batch_get_status: 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 Gemini MCP Server. Nothing to install.
batch_get_status 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 batch_get_status 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 batch_get_status. 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.
batch_get_status is provided by the Gemini MCP Server MCP server (mintmcqueen/gemini-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 →