CANCEL BATCH JOB - Request cancellation of running batch job. WORKFLOW: 1) Sends cancel request to Gemini API, 2) Job transitions to CANCELLED state, 3) Processing stops (may take a few seconds), 4) Partial results may be available. USE CASE: Stop long-running job due to errors, changed requireme...
AI agents call batch_cancel to permanently remove resources in Gemini MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a batch job is an irreversible action — once cancelled, the job cannot be resumed. Any in-progress work is lost and the job transitions permanently to a CANCELLED state. While partial results may be available, the job itself cannot be restarted from where it left off, making this effectively irreversible.
From the tool's definition CANCEL BATCH JOB - Request cancellation of running batch job... Job transitions to CANCELLED state, 3) Processing stops... Cannot cancel SUCCEEDED or FAILED jobs
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
CANCEL BATCH JOB - Request cancellation of running batch job. WORKFLOW: 1) Sends cancel request to Gemini API, 2) Job transitions to CANCELLED state, 3) Processing stops (may take a few seconds), 4) Partial results may be available. USE CASE: Stop long-running job due to errors, changed requirements, or cost management. NOTE: Cannot cancel SUCCEEDED or FAILED jobs. It is categorised as a Destructive tool in the Gemini MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gemini MCP Server MCP server in PolicyLayer and add a rule for batch_cancel: 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_cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the batch_cancel 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_cancel. 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_cancel 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 →