Permanently batch delete messages by ID
Risk signalsIrreversible bulk message deletion
Part of the Google Workspace Gmail (gws CLI) server.
Free to start. No card required.
AI agents may call gmail_users_messages_batchDelete to permanently remove or destroy resources in Google Workspace Gmail (gws CLI). Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call gmail_users_messages_batchDelete in a loop, permanently destroying resources in Google Workspace Gmail (gws CLI). There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"gmail_users_messages_batchDelete"
]
}See the full Google Workspace Gmail (gws CLI) policy for all 79 tools.
These attack patterns abuse exactly the kind of access gmail_users_messages_batchDelete gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Permanently batch delete messages by ID. It is categorised as a Destructive tool in the Google Workspace Gmail (gws CLI) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Workspace Gmail (gws CLI) MCP server in PolicyLayer and add a rule for gmail_users_messages_batchDelete: 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 Google Workspace Gmail (gws CLI). Nothing to install.
gmail_users_messages_batchDelete 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_users_messages_batchDelete 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_users_messages_batchDelete. 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_users_messages_batchDelete is provided by the Google Workspace Gmail (gws CLI) MCP server (@gws mcp -s gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 79 Google Workspace Gmail (gws CLI) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.