delete-contact
Remove contact permanently. Returns: empty on success. Use when: deleting person from contacts. Note: permanent deletion, use resourceName from list/get.
This record as markdown: /tools/199-biotechnologies-mcp-google/delete-contact.md
What delete-contact does on MCP Google Workspace
AI agents call delete-contact to permanently remove resources in MCP Google Workspace, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-contact is rated Critical
This tool performs irreversible deletion of contact records. Even though the blast radius is somewhat limited to contact data rather than broader system resources, the permanent nature of the action and inability to undo it classifies this as Destructive.
From the tool's definition Tool description explicitly states 'Remove contact permanently' and 'permanent deletion'. The tool irreversibly deletes contact data from Google Contacts.
Attacks that exploit this kind of access
The rule that runs delete-contact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-contact, this is the rule to start with:
delete-contact 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 MCP Google Workspace, apply this rule, and every delete-contact call is checked against it from then on.
Questions about delete-contact
Remove contact permanently. Returns: empty on success. Use when: deleting person from contacts. Note: permanent deletion, use resourceName from list/get. It is categorised as a Destructive tool in the MCP Google Workspace MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for delete-contact: 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 MCP Google Workspace. Nothing to install.
delete-contact 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 delete-contact 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 delete-contact. 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.
delete-contact is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Workspace, and thousands of servers like it.
Across the catalogue