AI agents call prompthub_whoami to retrieve information from Prompthub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns identity/authentication information about the current user. It has no side effects, modifies nothing, and simply retrieves who is authenticated. Misuse potential is minimal.
From the tool's definition Verify the configured PromptHub token and return the authenticated user
Attacks that exploit this kind of access
Verify the configured PromptHub token and return the authenticated user. It is categorised as a Read tool in the Prompthub MCP Server, which means it retrieves data without modifying state.
Register the Prompthub MCP server in PolicyLayer and add a rule for prompthub_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 Prompthub. Nothing to install.
prompthub_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 prompthub_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 prompthub_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.
prompthub_whoami is provided by the Prompthub MCP server (lionelhao/prompthub-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 →