This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/wp-me.md
What wp_me does on Wordpress
AI agents call wp_me to retrieve information from Wordpress without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wp_me is rated Low
This tool performs a read-only operation to fetch metadata about the current user. It has no side effects, cannot modify data, and poses minimal risk even if called by an AI agent. The blast radius is limited to potential information disclosure of user identity, which is low severity.
From the tool's definition Tool name 'wp_me' and description 'Get the currently authenticated user' indicate a query operation that retrieves information about the authenticated user without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs wp_me safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_me, this is the rule to start with:
wp_me 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 Wordpress, apply this rule, and every wp_me call is checked against it from then on.
Questions about wp_me
Get the currently authenticated user. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Wordpress MCP server in PolicyLayer and add a rule for wp_me: 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 Wordpress. Nothing to install.
wp_me 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 wp_me 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 wp_me. 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.
wp_me is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue