DELETE a Google contact by resourceName.
AI agents call delete_contact to permanently remove resources in Nexus Core — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a contact from Google Contacts. The action cannot be undone and results in data loss. While the blast radius is limited to a single contact record (not systemic), the irreversible nature of deletion places it in the Destructive category, which ranks above Execute, Write, and Read.
From the tool's definition Tool name is 'delete_contact' and description states 'DELETE a Google contact by resourceName' — uses the word DELETE which indicates irreversible removal of data.
Attacks that exploit this kind of access
DELETE a Google contact by resourceName. It is categorised as a Destructive tool in the Nexus Core MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nexus Core 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 Nexus Core. 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 Nexus Core MCP server (noumenon-ai/nexus-core). 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 →