wordpress_plugin_exists
AI agents call wordpress_plugin_exists 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.
The name strongly suggests this is a query/check operation to determine plugin existence, which is a read-only operation that retrieves information without creating, modifying, or deleting anything. The empty description prevents confirmation of exact behavior, but the naming convention and the function's logical purpose (existence check) clearly map to the Read category.
From the tool's definition Tool name 'wordpress_plugin_exists' indicates a check operation that queries whether a plugin exists, returning a boolean result with no side effects.
Attacks that exploit this kind of access
wordpress_plugin_exists. 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_plugin_exists: 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_plugin_exists 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_plugin_exists 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_plugin_exists. 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_plugin_exists 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.
wordpress_plugin_exists is one line of WordPress MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →