gmail_users_settings_cse_keypairs_obliterate
Permanently destroy a CSE keypair
This record as markdown: /tools/google-workspace-gmail/gmail-users-settings-cse-keypairs-obliterate.md
What gmail_users_settings_cse_keypairs_obliterate does on Google Workspace Gmail (gws CLI)
AI agents call gmail_users_settings_cse_keypairs_obliterate to permanently remove resources in Google Workspace Gmail (gws CLI), typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why gmail_users_settings_cse_keypairs_obliterate is rated Critical
This tool permanently deletes Client-Side Encryption (CSE) keypairs, which cannot be undone. Destruction of encryption keys is a destructive action with significant blast radius: loss of the keypair means loss of ability to decrypt historical encrypted emails, rendering them unrecoverable. An AI agent misusing this tool could cause permanent data loss for users.
From the tool's definition Tool name contains 'obliterate' and description states 'Permanently destroy a CSE keypair' — both indicate irreversible deletion of cryptographic key material.
Risk signalsEncrypted messages become unreadable
Attacks that exploit this kind of access
The rule that runs gmail_users_settings_cse_keypairs_obliterate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Workspace Gmail (gws CLI), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gmail_users_settings_cse_keypairs_obliterate, this is the rule to start with:
gmail_users_settings_cse_keypairs_obliterate is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Workspace Gmail (gws CLI), apply this rule, and every gmail_users_settings_cse_keypairs_obliterate call is checked against it from then on.
Questions about gmail_users_settings_cse_keypairs_obliterate
Permanently destroy a CSE keypair. 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_settings_cse_keypairs_obliterate: 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_settings_cse_keypairs_obliterate 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_settings_cse_keypairs_obliterate 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_settings_cse_keypairs_obliterate. 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_settings_cse_keypairs_obliterate 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.
More on Google Workspace Gmail (gws CLI), and thousands of servers like it.
Across the catalogue