remove_agent_contact
AI agents call remove_agent_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.
Based on the naming convention 'remove_agent_contact', this tool likely irreversibly removes a contact association from an agent identity. The 'remove' verb typically implies deletion/destructive action. However, the empty description significantly lowers confidence, as it could also be a reversible unlink operation.
From the tool's definition Tool name: remove_agent_contact; description is empty and uninformative.
Attacks that exploit this kind of access
remove_agent_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_agent_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_agent_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_agent_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_agent_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_agent_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 →