DELETE BATCH JOB - Permanently delete batch job and associated data. WORKFLOW: 1) Validates job exists, 2) Deletes job metadata from Gemini API, 3) Removes from internal tracking. USE CASE: Clean up completed/failed jobs, manage job history, free storage. WARNING: Irreversible operation. Results ...
AI agents call batch_delete 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.
This tool irreversibly deletes data (batch job metadata, associated results, and internal tracking) that cannot be recovered or undone. While the blast radius is somewhat contained to batch job artifacts rather than user data, the irreversible deletion of processing results and job state qualifies it as Destructive rather than Write.
From the tool's definition Tool description explicitly states: 'Permanently delete batch job and associated data' and 'WARNING: Irreversible operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
DELETE BATCH JOB - Permanently delete batch job and associated data. WORKFLOW: 1) Validates job exists, 2) Deletes job metadata from Gemini API, 3) Removes from internal tracking. USE CASE: Clean up completed/failed jobs, manage job history, free storage. WARNING: Irreversible operation. Results will be lost if not downloaded first. Recommended to download results before deletion. 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_delete: 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_delete 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_delete 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_delete. 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_delete 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 →