wp_list_plugins

Zeigt alle installierten WordPress-Plugins an

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/c-sakel-wp-mcp-server/wp-list-plugins.md

WHAT IT DOES

What wp_list_plugins does on WordPress MCP Server

AI agents call wp_list_plugins to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why wp_list_plugins is rated Low

This tool retrieves and displays information about installed plugins. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an AI agent using this tool can only view which plugins are installed, which is non-sensitive metadata in most contexts.

From the tool's definition Tool name 'wp_list_plugins' and description 'Zeigt alle installierten WordPress-Plugins an' (Shows all installed WordPress plugins) indicate a listing/retrieval operation with no modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wp_list_plugins safely

PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_list_plugins, this is the rule to start with:

wp_list_plugins Allowed

wp_list_plugins is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wp_list_plugins": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every wp_list_plugins call is checked against it from then on.

FAQ

Questions about wp_list_plugins

What does the wp_list_plugins tool do? +

Zeigt alle installierten WordPress-Plugins an. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wp_list_plugins? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wp_list_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 WordPress MCP Server. Nothing to install.

What risk level is wp_list_plugins? +

wp_list_plugins is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wp_list_plugins? +

Yes. Add a rate_limit block to the wp_list_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.

How do I block wp_list_plugins completely? +

Set action: deny in the PolicyLayer policy for wp_list_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.

What MCP server provides wp_list_plugins? +

wp_list_plugins is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →