whoami
Read the upstream IdP token via orchestration (remote-proxy mode)
This record as markdown: /tools/frontmcp/whoami.md
What whoami does on Frontmcp
AI agents call whoami to retrieve information from Frontmcp 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 queries identity provider (IdP) token information for the authenticated user. It is a read-only operation that retrieves existing authentication data without creating, modifying, deleting, or executing external actions.
From the tool's definition Tool name 'whoami' and description 'Read the upstream IdP token via orchestration' explicitly uses the verb 'Read' and retrieves authentication token data without modification.
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 Frontmcp, 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 Frontmcp, apply this rule, and every whoami call is checked against it from then on.
Questions about whoami
Read the upstream IdP token via orchestration (remote-proxy mode). It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front 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 Frontmcp. 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 Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue