Retrieve a list of chat conversations
AI agents call get_chats to retrieve information from VoIPBin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing chat conversation data without creating, modifying, deleting, or executing any operations. It falls squarely into the Read category. Severity is low because retrieving chat metadata poses minimal risk even if misused by an AI agent—the worst outcome would be unauthorized data access, which is a confidentiality concern but not immediately damaging.
From the tool's definition Tool name 'get_chats' and description 'Retrieve a list of chat conversations' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieve a list of chat conversations. It is categorised as a Read tool in the VoIPBin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VoIPBin MCP Server MCP server in PolicyLayer and add a rule for get_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 VoIPBin MCP Server. Nothing to install.
get_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 get_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 get_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.
get_chats is provided by the VoIPBin MCP Server MCP server (nrjchnd/voipbin-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 →