Get list of users with Claude Code conversation history on this machine
AI agents call get_claude_users 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 retrieves a list of users and their conversation history metadata from the local machine. While classified as Read (no data modification), the severity is high because: (1) it exposes user identity and conversation metadata across all users on a shared machine, enabling surveillance or privacy violations; (2) conversation history may contain sensitive information (API keys, credentials, private…
From the tool's definition Tool name 'get_claude_users' and description 'Get list of users with Claude Code conversation history on this machine' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Get list of users with Claude Code conversation history on this machine. 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_claude_users: 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_claude_users 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_claude_users 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_claude_users. 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_claude_users 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 →