See which other Claude Code agents are currently active. Shows their code, project, and uptime. Use this BEFORE starting work to check if other agents are working on the same project. Use this to find an agent
AI agents call who to retrieve information from Claude Intercom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure reconnaissance/query tool that retrieves metadata about active agents without side effects. The most severe risk is that an agent could learn about other agents' projects, but this is informational only and low-severity in a collaborative context. Classified as Read with low severity and high confidence.
From the tool's definition Tool 'who' returns information about active Claude Code agents (code, project, uptime). The description uses passive retrieval language: 'See which', 'Shows', 'find an agent'. No mutations, deletions, executions, or state changes are implied.
Attacks that exploit this kind of access
See which other Claude Code agents are currently active. Shows their code, project, and uptime. Use this BEFORE starting work to check if other agents are working on the same project. Use this to find an agent. It is categorised as a Read tool in the Claude Intercom MCP Server, which means it retrieves data without modifying state.
Register the Claude Intercom MCP server in PolicyLayer and add a rule for who: 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 Intercom. Nothing to install.
who 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 who 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 who. 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.
who is provided by the Claude Intercom MCP server (sanztheo/claude-intercom). 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 →