Show which PromptingBox account is connected to this MCP server.
AI agents call whoami to retrieve information from PromptingBox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely queries and returns the identity of the currently connected account. It is a read-only operation that retrieves information without creating, modifying, or deleting any data. The blast radius of misuse is minimal—an agent would only learn which account is active, which poses no direct security or operational risk. This is a classic 'Read' category operation.
From the tool's definition Tool name 'whoami' and description 'Show which PromptingBox account is connected to this MCP server' indicates retrieval of account identity information with no side effects or modifications.
Attacks that exploit this kind of access
Show which PromptingBox account is connected to this MCP server. It is categorised as a Read tool in the PromptingBox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PromptingBox 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 PromptingBox 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 PromptingBox MCP Server MCP server (promptingbox/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 →