Delete a FluentCRM list
AI agents call fcrm_delete_list 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 deletes an entire list object from FluentCRM, which cannot be undone. Deletion operations are classified as Destructive per the categorization rules. The high severity reflects that losing a list could impact email campaigns, segmentation, or member organization in the community platform, potentially affecting workflow and data integrity.
From the tool's definition Tool name contains 'delete' and description states 'Delete a FluentCRM list' — a permanent, irreversible removal of data structure and its contents.
Attacks that exploit this kind of access
Delete a FluentCRM list. 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 fcrm_delete_list: 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.
fcrm_delete_list 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 fcrm_delete_list 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 fcrm_delete_list. 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.
fcrm_delete_list 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 →