wordpress_list_plugin_files
AI agents call wordpress_list_plugin_files to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' verb combined with 'plugin_files' indicates this tool retrieves and queries plugin file information without any capability to modify, delete, or execute operations. This is a straightforward read operation with minimal risk. Confidence is slightly reduced due to the empty description, but the function name itself is sufficiently indicative of a read-only operation.
From the tool's definition Tool name contains 'list' which indicates data retrieval without modification. Description is empty, but the function name 'wordpress_list_plugin_files' clearly indicates a listing/querying operation that returns file information about plugins.
Attacks that exploit this kind of access
wordpress_list_plugin_files. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_list_plugin_files: 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.
wordpress_list_plugin_files 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 wordpress_list_plugin_files 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 wordpress_list_plugin_files. 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.
wordpress_list_plugin_files is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/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 →