Deletes content of any type
AI agents call delete_content 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 irreversibly removes data and cannot be undone, meeting the definition of Destructive. While the blast radius depends on what content is deleted, the capability to delete 'any type' suggests it could impact user-generated content, community posts, and other critical data in a WordPress multisite community environment.
From the tool's definition Tool name 'delete_content' combined with description 'Deletes content of any type' indicates irreversible deletion of data. The sibling tools list confirms this server manages WordPress community content including posts, spaces, and comments.
Attacks that exploit this kind of access
Deletes content of any type. 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_content: 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_content 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_content 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_content. 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_content 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 →