wordpress_check_user_capability
AI agents call wordpress_check_user_capability 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 appears to query or verify user permissions/capabilities on a WordPress site. The 'check_' prefix typically denotes a read-only verification operation that retrieves capability status without side effects. No description is provided, which reduces confidence slightly, but the semantic meaning of 'check capability' strongly implies a non-mutating query operation.
From the tool's definition Tool name 'wordpress_check_user_capability' suggests a capability/permission query operation; description is empty but the naming pattern (check_*) indicates information retrieval rather than modification or execution.
Attacks that exploit this kind of access
wordpress_check_user_capability. 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 wordpress_check_user_capability: 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.
wordpress_check_user_capability 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 wordpress_check_user_capability 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 wordpress_check_user_capability. 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.
wordpress_check_user_capability is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/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 →