New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_contact

Delete a contact by resource name.

SERVERMCP Google Contacts Server SOURCE4tal/mcp-google-contacts
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/4tal-mcp-google-contacts/delete-contact.md

What delete_contact does on MCP Google Contacts Server

AI agents call delete_contact to permanently remove resources in MCP Google Contacts Server, 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 permanently removes contact records from Google Contacts without the ability to undo the operation through normal means. Deletion is irreversible and represents a loss of data. While not as critical as financial or organizational-level destructive actions, deleting user contacts has significant impact on data integrity and user operations.

From the tool's definition Tool name is 'delete_contact' and description states 'Delete a contact by resource name' - the verb 'Delete' explicitly indicates irreversible data removal.

Questions about delete_contact

What does the delete_contact tool do? +

Delete a contact by resource name. It is categorised as a Destructive tool in the MCP Google Contacts Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_contact? +

Register the MCP Google Contacts Server 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 Contacts Server. Nothing to install.

What risk level is delete_contact? +

delete_contact is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_contact? +

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.

How do I block delete_contact completely? +

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.

What MCP server provides delete_contact? +

delete_contact is provided by the MCP Google Contacts Server MCP server (4tal/mcp-google-contacts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on MCP Google Contacts Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Google Contacts Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.