This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/wp-get-plugin.md
What wp_get_plugin does on Wordpress
AI agents call wp_get_plugin 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_get_plugin is rated Low
This tool queries and retrieves plugin information without modifying, deleting, or executing anything. It has minimal blast radius—an AI agent misusing it can only access existing plugin metadata, which poses no security, financial, or operational risk. This is a classic Read category tool.
From the tool's definition Tool name 'wp_get_plugin' and description 'Get plugin details by slug' indicate a retrieval operation with no side effects. The verb 'Get' and the singular retrieval pattern confirm this is a read-only operation.
Attacks that exploit this kind of access
The rule that runs wp_get_plugin 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_get_plugin, this is the rule to start with:
wp_get_plugin 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_get_plugin call is checked against it from then on.
Questions about wp_get_plugin
Get plugin details by slug. 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_get_plugin: 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_get_plugin 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_get_plugin 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_get_plugin. 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_get_plugin 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