❌ Cancel any pending operation (email, file share, calendar event, bulk operation)
AI agents call cancel_operation to permanently remove resources in Google — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a pending operation is irreversible in most contexts — once an email send, file share, calendar event creation, or bulk operation is cancelled, the pending action is aborted and cannot be recovered. The broad scope ('any pending operation') across multiple services (email, file share, calendar, bulk) amplifies the blast radius significantly.
From the tool's definition Cancel any pending operation (email, file share, calendar event, bulk operation)
Attacks that exploit this kind of access
❌ Cancel any pending operation (email, file share, calendar event, bulk operation). It is categorised as a Destructive tool in the Google MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google MCP server in PolicyLayer and add a rule for cancel_operation: 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. Nothing to install.
cancel_operation 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 cancel_operation 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 cancel_operation. 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.
cancel_operation is provided by the Google MCP server (robcerda/google-mcp-server). 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 →