Returns the identity the current session is authenticated as on the targeted wiki: the username, whether the session is anonymous (no user is logged in), and the user groups it belongs to. Set includeRights to also return the full list of user rights. Use to confirm who edits and uploads will be ...
AI agents call whoami to retrieve information from MediaWiki MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves authentication/session information (username, groups, rights) with no side effects. It is a pure read/query operation analogous to a 'get current user' endpoint.
From the tool's definition Returns the identity the current session is authenticated as...the username, whether the session is anonymous...and the user groups it belongs to
Documented attack patterns abuse exactly the kind of access whoami gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MediaWiki MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for whoami:
{
"version": "1",
"default": "deny",
"tools": {
"whoami": {}
}
}whoami is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the identity the current session is authenticated as on the targeted wiki: the username, whether the session is anonymous (no user is logged in), and the user groups it belongs to. Set includeRights to also return the full list of user rights. Use to confirm who edits and uploads will be attributed to before writing — for example, to resolve your own username before building a title under your own user namespace (User:<username>/…). Reports anonymous access rather than failing when the session has no credentials. For which wikis have stored OAuth tokens and their scopes, use oauth-status instead. It is categorised as a Read tool in the MediaWiki MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MediaWiki 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 MediaWiki 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 MediaWiki MCP Server MCP server (@professional-wiki/mediawiki-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MediaWiki MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 MediaWiki MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.