Move multiple Gmail messages to trash in a single call (up to 50). Use after gmail_search to bulk-clean spam or old notifications. Returns a count of successfully trashed vs failed messages.
AI agents call gmail_batch_trash to permanently remove resources in Access — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Trashing up to 50 emails in one operation is a high-blast-radius destructive action. While Gmail trash can technically be restored within 30 days, the tool is designed for bulk deletion of messages and is described as a 'bulk-clean' mechanism. The scale (50 at a time) and irreversible intent (trashing) places this firmly in Destructive. An AI agent misusing this could silently discard important emails at scale.
From the tool's definition Move multiple Gmail messages to trash in a single call (up to 50)... bulk-clean spam or old notifications
Attacks that exploit this kind of access
Move multiple Gmail messages to trash in a single call (up to 50). Use after gmail_search to bulk-clean spam or old notifications. Returns a count of successfully trashed vs failed messages. It is categorised as a Destructive tool in the Access MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Access MCP server in PolicyLayer and add a rule for gmail_batch_trash: 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 Access. Nothing to install.
gmail_batch_trash 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 gmail_batch_trash 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 gmail_batch_trash. 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.
gmail_batch_trash is provided by the Access MCP server (scottpedia0/access). 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 →