Vitally tool to get recent conversations for an account
AI agents call get_account_conversations to retrieve information from Vitally 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 conversation data without side effects. It does not create, modify, delete, or execute any operations—it simply fetches recent conversations for an account. While the data retrieved may be sensitive (customer communications), the tool itself performs no destructive or state-changing action.
From the tool's definition Tool is named 'get_account_conversations' and described as 'to get recent conversations for an account'. The verb 'get' and the action of retrieving historical conversation data indicate a read-only operation with no modification of data.
Attacks that exploit this kind of access
Vitally tool to get recent conversations for an account. It is categorised as a Read tool in the Vitally MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vitally MCP Server MCP server in PolicyLayer and add a rule for get_account_conversations: 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 Vitally MCP Server. Nothing to install.
get_account_conversations 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_account_conversations 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_account_conversations. 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_account_conversations is provided by the Vitally MCP Server MCP server (johnjjung/vitally-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 →