Send a FluentCRM campaign
AI agents invoke fcrm_send_campaign to trigger actions in FluentCommunity Manager. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending a campaign is an irreversible external operation that dispatches bulk communications to potentially many recipients. It is not purely a data write (it triggers real-world email delivery), not financial, and not destructive in the data-deletion sense. Execute is the most appropriate category given the external side effects.
From the tool's definition 'Send a FluentCRM campaign' — triggers an external email/marketing campaign operation whose effects (mass email delivery to subscribers) depend on arguments
Attacks that exploit this kind of access
Send a FluentCRM campaign. It is categorised as a Execute tool in the FluentCommunity Manager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for fcrm_send_campaign: 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_send_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fcrm_send_campaign 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_send_campaign. 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_send_campaign 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 →