Deletes a media item
AI agents call delete_media to permanently remove resources in FluentCommunity Manager — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on media files/assets, which is a destructive action. While the blast radius is high (loss of media content), it is somewhat contained compared to critical severity since it affects individual media items rather than entire systems or financial transactions. Confidence is high because the name and description are explicit and unambiguous.
From the tool's definition The tool is explicitly named 'delete_media' with description 'Deletes a media item', indicating irreversible deletion of data. The action cannot be undone without restoration from backups.
Attacks that exploit this kind of access
Deletes a media item. It is categorised as a Destructive tool in the FluentCommunity Manager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FluentCommunity Manager 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 FluentCommunity Manager. 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 FluentCommunity Manager MCP server (wplaunchify/fluent-community-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 →