Reject a received contact request.
AI agents use reject_contact_request 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.
This is a reversible state modification (Write category). Rejecting a contact request does not permanently delete data—the request record remains and could theoretically be re-submitted or the decision reversed through other means. The action changes metadata/status rather than destroying information.
From the tool's definition Tool name 'reject_contact_request' and description 'Reject a received contact request' indicate the tool modifies the state of a contact request by changing its status from pending to rejected.
Attacks that exploit this kind of access
Reject a received contact request. 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 reject_contact_request: 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.
reject_contact_request 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 reject_contact_request 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 reject_contact_request. 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.
reject_contact_request 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 →