whoami
Return the profile of the currently authenticated PostKing user (email, plan, credit balance, token source).
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/whoami.md
What whoami does on Postking Mcp
AI agents call whoami to retrieve information from Postking Mcp 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 only reads and returns information about the authenticated user. It performs no writes, executions, or destructive actions. The data returned (email, plan, credit balance, token source) is informational only. Misuse potential is minimal — an attacker could learn the user's email or plan tier, but cannot cause harm beyond information disclosure.
From the tool's definition 'Return the profile of the currently authenticated PostKing user (email, plan, credit balance, token source)' — purely retrieves user profile data with no side effects
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 Postking Mcp, 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 Postking Mcp, apply this rule, and every whoami call is checked against it from then on.
Questions about whoami
Return the profile of the currently authenticated PostKing user (email, plan, credit balance, token source). It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking 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 Postking Mcp. 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 Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
This server
Across the catalogue