Get detailed information about a specific plugin
AI agents call get_plugin_info to retrieve information from WordPress Plugin Directory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves plugin metadata/information from the WordPress.org plugin directory. It has no side effects, does not modify data, execute code, or trigger external operations. The verb 'Get' and the informational nature of the operation confirm it is a Read category tool with low severity risk.
From the tool's definition Tool is named 'get_plugin_info' with description 'Get detailed information about a specific plugin' — retrieves data about a plugin without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Get detailed information about a specific plugin. It is categorised as a Read tool in the WordPress Plugin Directory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress Plugin Directory MCP Server MCP server in PolicyLayer and add a rule for get_plugin_info: 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 Plugin Directory MCP Server. Nothing to install.
get_plugin_info 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_plugin_info 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_plugin_info. 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_plugin_info is provided by the WordPress Plugin Directory MCP Server MCP server (juanma-wp/wordpress-org-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 →