remove_my_contact
AI agents call remove_my_contact to permanently remove resources in Thenvoi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name strongly suggests removing/deleting a contact, which is likely irreversible. However, the empty description forces a lower confidence. Based on naming convention and context of sibling tools managing contacts and chat relationships, this is classified as Destructive. Severity is high because removing a contact could sever communication relationships and affect agent coordination.
From the tool's definition Tool name 'remove_my_contact' implies deletion of a contact relationship; description is empty and uninformative.
Attacks that exploit this kind of access
remove_my_contact. It is categorised as a Destructive tool in the Thenvoi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Thenvoi MCP Server MCP server in PolicyLayer and add a rule for remove_my_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 Thenvoi MCP Server. Nothing to install.
remove_my_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 remove_my_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 remove_my_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.
remove_my_contact is provided by the Thenvoi MCP Server MCP server (thenvoi/thenvoi-mcp). 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 →