fc_bulk_delete_posts

Delete multiple FluentCommunity posts at once

Server FluentCommunity Manager wplaunchify/fluent-community-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What fc_bulk_delete_posts does on FluentCommunity Manager

AI agents call fc_bulk_delete_posts 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.

Why fc_bulk_delete_posts needs a policy

This tool irreversibly deletes data (posts) and cannot be undone. Deletion operations are inherently destructive. The bulk nature of the operation (multiple posts at once) increases severity from medium to high, as an agent mistake could eliminate substantial content. Destructive is the most severe applicable category and takes precedence over any Write classification.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete multiple FluentCommunity posts at once'. The bulk operation amplifies the destructive impact by enabling deletion of multiple items in a single call.

Questions about fc_bulk_delete_posts

What does the fc_bulk_delete_posts tool do? +

Delete multiple FluentCommunity posts at once. 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.

How do I enforce a policy on fc_bulk_delete_posts? +

Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for fc_bulk_delete_posts: 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.

What risk level is fc_bulk_delete_posts? +

fc_bulk_delete_posts is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit fc_bulk_delete_posts? +

Yes. Add a rate_limit block to the fc_bulk_delete_posts 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.

How do I block fc_bulk_delete_posts completely? +

Set action: deny in the PolicyLayer policy for fc_bulk_delete_posts. 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.

What MCP server provides fc_bulk_delete_posts? +

fc_bulk_delete_posts 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.