Get Claude Code conversations with optional filters (username, search text, project, date range)
AI agents call get_conversations to retrieve information from Claude Viewer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and retrieves conversation data without side effects, placing it in the Read category. However, severity is high because: (1) it can access conversations across ALL users on a machine without apparent per-user access controls, (2) conversations may contain sensitive information (API keys, credentials, proprietary code, personal data), (3) the filter options allow targeted extraction of specific…
From the tool's definition get_conversations retrieves Claude Desktop/Code conversation history with optional filters (username, search text, project, date range).
Attacks that exploit this kind of access
Get Claude Code conversations with optional filters (username, search text, project, date range). It is categorised as a Read tool in the Claude Viewer MCP Server, which means it retrieves data without modifying state.
Register the Claude Viewer MCP server in PolicyLayer and add a rule for get_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 Claude Viewer. Nothing to install.
get_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_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_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_conversations is provided by the Claude Viewer MCP server (maxturazzini/claude-viewer). 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 →