AI agents call whoami to retrieve information from Healow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing authentication token claims to identify the current user/patient context. It has no side effects, does not create, modify, or delete data, and does not trigger external operations or financial transactions. The blast radius is minimal—misuse would only expose already-issued identity claims to the user running the query. It is correctly categorized as Read.
From the tool's definition Tool description states 'Return the id_token claims' - a read operation that retrieves and returns identity/context information without modifying any data.
Attacks that exploit this kind of access
Return the id_token claims for a connected practice (patient/user context). It is categorised as a Read tool in the Healow MCP Server, which means it retrieves data without modifying state.
Register the Healow MCP server in PolicyLayer and add a rule for whoami: 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 Healow. Nothing to install.
whoami 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 whoami 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 whoami. 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.
whoami is provided by the Healow MCP server (voysi-ia/healow-mcp-server). 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 →