resume_campaign
Resume a paused campaign. Only campaigns in paused status can be resumed. Optionally spread the remaining delivery over a number of hours.
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/resume-campaign.md
What resume_campaign does on Sequenzy Mcp
AI agents invoke resume_campaign to trigger actions in Sequenzy Mcp. 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.
Why resume_campaign is rated High
Resuming a campaign triggers external operations — specifically, it initiates the delivery/sending of emails to subscribers. This is an execution of an ongoing process with real-world side effects (emails sent to recipients), rather than a simple data write or read. Misuse could result in unintended mass email delivery.
From the tool's definition Resume a paused campaign... Only campaigns in paused status can be resumed. Optionally spread the remaining delivery over a number of hours.
Attacks that exploit this kind of access
The rule that runs resume_campaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resume_campaign, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every resume_campaign call is checked against it from then on.
Questions about resume_campaign
Resume a paused campaign. Only campaigns in paused status can be resumed. Optionally spread the remaining delivery over a number of hours. It is categorised as a Execute tool in the Sequenzy Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sequenzy MCP server in PolicyLayer and add a rule for 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 Sequenzy Mcp. Nothing to install.
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 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 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.
resume_campaign is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
Across the catalogue