claudeus_wp_plugins__list
List all installed WordPress plugins. View active, inactive, and network-active plugins with details.
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-plugins--list.md
What claudeus_wp_plugins__list does on Claudeus WordPress MCP
AI agents call claudeus_wp_plugins__list to retrieve information from Claudeus WordPress MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why claudeus_wp_plugins__list is rated Low
This tool queries and retrieves information about installed plugins. It has no side effects, creates no changes, executes no code, and performs no destructive actions. It is purely informational, fitting the 'Read' category for data retrieval operations.
From the tool's definition Tool name contains 'list' and description states 'List all installed WordPress plugins. View active, inactive, and network-active plugins with details.' This is a read-only operation that retrieves plugin metadata without modifying, executing, or deleting any…
Attacks that exploit this kind of access
The rule that runs claudeus_wp_plugins__list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claudeus WordPress MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claudeus_wp_plugins__list, this is the rule to start with:
claudeus_wp_plugins__list 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 Claudeus WordPress MCP, apply this rule, and every claudeus_wp_plugins__list call is checked against it from then on.
Questions about claudeus_wp_plugins__list
List all installed WordPress plugins. View active, inactive, and network-active plugins with details. It is categorised as a Read tool in the Claudeus WordPress MCP MCP Server, which means it retrieves data without modifying state.
Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_plugins__list: 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 Claudeus WordPress MCP. Nothing to install.
claudeus_wp_plugins__list 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 claudeus_wp_plugins__list 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 claudeus_wp_plugins__list. 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.
claudeus_wp_plugins__list is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claudeus WordPress, and thousands of servers like it.
This server
Across the catalogue