whoami
Returns information about the authenticated user
This record as markdown: /tools/mcp-test-servers/whoami.md
What whoami does on Mcp Test Servers
AI agents call whoami to retrieve information from Mcp Test Servers without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why whoami is rated Low
This tool retrieves authentication/identity data about the current user. It is a read-only operation with no side effects, no data modification, no code execution, and no financial impact. The blast radius of misuse is minimal—an attacker could learn about the authenticated identity but cannot escalate privileges or cause damage through this tool alone.
From the tool's definition Tool name 'whoami' and description 'Returns information about the authenticated user' indicate a query operation that retrieves user identity information without modifying state.
Attacks that exploit this kind of access
The rule that runs whoami safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Test Servers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For whoami, this is the rule to start with:
whoami 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 Mcp Test Servers, apply this rule, and every whoami call is checked against it from then on.
Questions about whoami
Returns information about the authenticated user. It is categorised as a Read tool in the Mcp Test Servers MCP Server, which means it retrieves data without modifying state.
Register the Mcp Test Servers 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 Mcp Test Servers. 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 Mcp Test Servers MCP server (msfeldstein/mcp-test-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Test Servers, and thousands of servers like it.
This server
Across the catalogue