cancel_sequence_enrollments
Cancel active/waiting enrollments in one sequence. Provide sequenceId and exactly one target: cancelAll to drain every active/waiting enrollment (use this to fully stop a live sequence instead of only freezing enrollment), subscriberIds for a specific batch, subscriberId for one subscriber, or fi...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/cancel-sequence-enrollments.md
What cancel_sequence_enrollments does on Sequenzy Mcp
AI agents call cancel_sequence_enrollments to permanently remove resources in Sequenzy Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_sequence_enrollments is rated Critical
Cancelling enrollments is an irreversible action that removes subscribers from active sequences. There is no indication of an undo mechanism. The 'cancelAll' option can drain every enrollment from a live sequence, representing a high blast radius. The bulk nature and the explicit 'dryRun false' requirement to execute confirm destructive intent.
From the tool's definition Cancel active/waiting enrollments...cancelAll to drain every active/waiting enrollment...fully stop a live sequence...bulk cancellation
Attacks that exploit this kind of access
The rule that runs cancel_sequence_enrollments 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 cancel_sequence_enrollments, this is the rule to start with:
cancel_sequence_enrollments is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every cancel_sequence_enrollments call is checked against it from then on.
Questions about cancel_sequence_enrollments
Cancel active/waiting enrollments in one sequence. Provide sequenceId and exactly one target: cancelAll to drain every active/waiting enrollment (use this to fully stop a live sequence instead of only freezing enrollment), subscriberIds for a specific batch, subscriberId for one subscriber, or fieldValues to match stored entry event properties. Every bulk target defaults to dryRun, so pass dryRun false to actually cancel. Bulk cancellation is capped per call: while the response reports remainingCount above zero, call again with the same arguments until it reaches zero. It is categorised as a Destructive tool in the Sequenzy Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sequenzy MCP server in PolicyLayer and add a rule for cancel_sequence_enrollments: 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.
cancel_sequence_enrollments 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 cancel_sequence_enrollments 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 cancel_sequence_enrollments. 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.
cancel_sequence_enrollments 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