Return the authenticated account's identity and QR-code count (GET /me).
AI agents call whoami to retrieve information from QR Forge MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple identity lookup and retrieves account metadata. It has no side effects, creates no resources, modifies no data, and poses minimal risk. While identity disclosure could theoretically aid reconnaissance, the information is already known to the authenticated user. Classified as Read with low severity due to the benign nature of self-identification queries.
From the tool's definition Tool description explicitly states 'Return the authenticated account's identity and QR-code count' with GET /me endpoint, indicating a read-only query operation that retrieves user account information without modification.
Attacks that exploit this kind of access
Return the authenticated account's identity and QR-code count (GET /me). It is categorised as a Read tool in the QR Forge MCP server MCP Server, which means it retrieves data without modifying state.
Register the QR Forge MCP server 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 QR Forge MCP server. 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 QR Forge MCP server MCP server (jkolarov/qrforge-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 →