Delete a media file in WordPress site.
AI agents call delete_media to permanently remove resources in WordPress MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes media files from a WordPress site with no undo capability. While the blast radius is somewhat contained (affects only media assets, not entire site integrity), the irreversible nature of deletion and potential impact on site functionality (broken image links, missing assets) classifies this as Destructive with high severity.
From the tool's definition Tool name and description: 'delete_media' - 'Delete a media file in WordPress site.' The verb 'delete' combined with 'media file' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a media file in WordPress site. It is categorised as a Destructive tool in the WordPress MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_media is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →