add_agent_contact
AI agents use add_agent_contact to create or update resources in Thenvoi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Thenvoi MCP Server environment.
The name 'add_agent_contact' indicates a reversible creation or modification of contact data rather than destructive deletion, code execution, or financial operations. Classified as Write because it creates or modifies contact records. Severity is medium due to potential for creating unauthorized contact relationships or spam.
From the tool's definition Tool name is 'add_agent_contact' with no description provided. Based on sibling tools like 'approve_contact_request', 'cancel_contact_request', and 'create_contact_request', this tool appears to create or modify contact relationships in the Thenvoi platform.
Attacks that exploit this kind of access
add_agent_contact. It is categorised as a Write tool in the Thenvoi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Thenvoi MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_agent_contact is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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 →