list_agent_chats
AI agents call list_agent_chats 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 is a standard convention for retrieval operations that enumerate existing resources. No side effects or modifications are implied. Although the description is empty, the naming pattern and context from related write/destructive operations on the server strongly indicate this is a read-only retrieval operation with minimal blast radius if misused.
From the tool's definition Tool name 'list_agent_chats' indicates a list/query operation. The server description mentions 'manage agent identities, create and participate in chat rooms' and sibling tools include multiple 'create' and 'add' operations, suggesting this tool retrieves or…
Attacks that exploit this kind of access
list_agent_chats. 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_chats: 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_chats 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_chats 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_chats. 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_chats 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 →