List agents that are IDLE (finished their work and ready for a new task).
AI agents call who_is_free to retrieve information from Claude Team MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays the current state of agents (which ones are idle/available). It has no side effects, does not modify data, does not execute code, and does not delete anything. It is a pure information-retrieval operation, fitting the Read category. The low severity reflects that misuse would only expose scheduling/availability information with minimal blast radius.
From the tool's definition Tool name 'who_is_free' and description 'List agents that are IDLE (finished their work and ready for a new task)' indicate a query operation that retrieves status information about agent availability without modifying or executing anything.
Attacks that exploit this kind of access
List agents that are IDLE (finished their work and ready for a new task). It is categorised as a Read tool in the Claude Team MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Team MCP server in PolicyLayer and add a rule for who_is_free: 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 Team MCP. Nothing to install.
who_is_free 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_is_free 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_is_free. 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_free is provided by the Claude Team MCP server (lakshan12367/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 →