Get all metadata of the current user in WordPress site, including roles and capabilities.
AI agents call get_me to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user metadata (roles and capabilities) without side effects. It is a Read operation. Severity is medium rather than low because exposing detailed user roles and capabilities to an unauthorized agent could inform privilege escalation attacks or help an attacker map the WordPress user hierarchy, though it does not directly cause harm by itself.
From the tool's definition Tool description explicitly states 'Get all metadata of the current user' — a retrieval operation with no modification or deletion. The word 'Get' and 'metadata' indicate a read-only query.
Attacks that exploit this kind of access
Get all metadata of the current user in WordPress site, including roles and capabilities. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for get_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 MCP Server. Nothing to install.
get_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 get_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 get_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.
get_me is provided by the WordPress MCP Server MCP server (obot-platform/wordpress-mcp-server). 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 →