wordpress_list_media
AI agents call wordpress_list_media to retrieve information from MCP Wordpress without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists media items, which is a read-only query operation with no side effects. It retrieves existing data without modification, creation, or deletion. Low severity because listing media poses minimal risk even if misused—it only exposes metadata about existing media assets.
From the tool's definition Tool name 'wordpress_list_media' indicates a listing/retrieval operation. Description is empty, but the naming convention and context among sibling tools (which include create/delete/get operations) clearly positions this as a data retrieval tool.
Attacks that exploit this kind of access
wordpress_list_media. It is categorised as a Read tool in the MCP Wordpress MCP Server, which means it retrieves data without modifying state.
Register the MCP Wordpress MCP server in PolicyLayer and add a rule for wordpress_list_media: 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 MCP Wordpress. Nothing to install.
wordpress_list_media 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_media 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_media. 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_media is provided by the MCP Wordpress MCP server (crunchtools/mcp-wordpress). 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 →