AI agents invoke fluentcrm_resume_campaign to trigger actions in FluentCRM MCP Server. 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.
Resuming a campaign triggers an active external operation — sending marketing emails to potentially large numbers of contacts. This is not merely a data write; it executes a workflow with real-world effects (email delivery). It falls under Execute due to triggering external operations, with high severity due to the blast radius of mass email sends that cannot be easily recalled.
From the tool's definition 'Wznawia kampanię' means 'Resumes a campaign' in Polish — this triggers an external operation (resuming an email marketing campaign), which causes emails to be sent to contacts.
Documented attack patterns abuse exactly the kind of access fluentcrm_resume_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FluentCRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for fluentcrm_resume_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"fluentcrm_resume_campaign": {
"limits": [
{
"counter": "fluentcrm_resume_campaign_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}fluentcrm_resume_campaign stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Wznawia kampanię. It is categorised as a Execute tool in the FluentCRM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FluentCRM MCP Server MCP server in PolicyLayer and add a rule for fluentcrm_resume_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 FluentCRM MCP Server. Nothing to install.
fluentcrm_resume_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 fluentcrm_resume_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 fluentcrm_resume_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.
fluentcrm_resume_campaign is provided by the FluentCRM MCP Server MCP server (netflyapp/fluentcrm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FluentCRM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 FluentCRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.