who
List agents present in the café (names only).
This record as markdown: /tools/a2a-mcp-world/who.md
What who does on A2A-MCP-World
AI agents call who to retrieve information from A2A-MCP-World without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why who is rated Low
This tool performs a passive lookup of available agents, returning read-only information about café occupants. It has no side effects, cannot modify state, and presents minimal risk even if invoked by an untrusted agent. The restriction to 'names only' further limits information leakage.
From the tool's definition Tool name 'who' and description 'List agents present in the café (names only)' indicate a query operation that retrieves and displays current state information without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs who safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A2A-MCP-World, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For who, this is the rule to start with:
who is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect A2A-MCP-World, apply this rule, and every who call is checked against it from then on.
Questions about who
List agents present in the café (names only). It is categorised as a Read tool in the A2A-MCP-World MCP Server, which means it retrieves data without modifying state.
Register the A2A-MCP-World 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 A2A-MCP-World. 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 A2A-MCP-World MCP server (akshaytp749/A2A-MCP-World). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A2A-MCP-World, and thousands of servers like it.
This server
Across the catalogue