get_wordpress_plugins
Get list of WordPress plugins for a hosting package
This record as markdown: /tools/cbrown35-20i-mcp/get-wordpress-plugins.md
What get_wordpress_plugins does on 20i MCP Server
AI agents call get_wordpress_plugins to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_wordpress_plugins is rated Low
This tool retrieves and lists WordPress plugins associated with a hosting package. It performs a read-only query with no ability to install, remove, modify, or execute plugins. The blast radius of misuse is minimal — an AI agent could only enumerate existing plugins, which does not compromise the hosting environment or user data. Classified as Read with low severity.
From the tool's definition Tool name includes 'get' and description states 'Get list of WordPress plugins' — a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_wordpress_plugins safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_wordpress_plugins, this is the rule to start with:
get_wordpress_plugins 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 20i MCP Server, apply this rule, and every get_wordpress_plugins call is checked against it from then on.
Questions about get_wordpress_plugins
Get list of WordPress plugins for a hosting package. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_wordpress_plugins: 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 20i MCP Server. Nothing to install.
get_wordpress_plugins 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_wordpress_plugins 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_wordpress_plugins. 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_wordpress_plugins is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue