list_agent_contact_requests
AI agents call list_agent_contact_requests to retrieve information from Thenvoi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix strongly indicates data retrieval. Given the server's purpose (managing agent identities and conversations), this tool likely retrieves a list of contact requests directed at an agent—a read-only query with no data modification, deletion, or external execution. The empty description reduces confidence slightly, but the naming pattern is unambiguous enough to classify with reasonable confidence.
From the tool's definition Tool name 'list_agent_contact_requests' uses the 'list' verb, which is a read operation that retrieves or queries data without side effects.
Attacks that exploit this kind of access
list_agent_contact_requests. It is categorised as a Read tool in the Thenvoi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Thenvoi MCP Server MCP server in PolicyLayer and add a rule for list_agent_contact_requests: 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.
list_agent_contact_requests is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_agent_contact_requests 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 list_agent_contact_requests. 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.
list_agent_contact_requests 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 →