List media files in WordPress site and get basic information of each media file.
AI agents call list_media 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.
This tool queries and returns information about media files without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk - the worst outcome of misuse would be information disclosure of media metadata already accessible to authenticated users. No side effects or blast radius beyond exposing existing data.
From the tool's definition Tool name 'list_media' and description 'List media files in WordPress site and get basic information of each media file' indicate a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
List media files in WordPress site and get basic information of each media file. 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 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 WordPress MCP Server. Nothing to install.
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 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 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.
list_media is provided by the WordPress MCP Server MCP server (obot-platform/wordpress-mcp-server). 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 →