disable_sequence
Disable/freeze a sequence. This blocks new enrollments and holds current recipients until the sequence is enabled again. To only stop new enrollments while current recipients continue, use pause_sequence_enrollments.
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/disable-sequence.md
What disable_sequence does on Sequenzy Mcp
AI agents use disable_sequence to create or update resources in Sequenzy Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sequenzy Mcp environment.
Why disable_sequence is rated Medium
This tool modifies the operational state of a sequence (disabling/freezing it), preventing new enrollments and pausing active recipients. The action is reversible (sequences can be re-enabled), so it falls under Write rather than Destructive. The blast radius is medium: disabling a sequence affects marketing workflows and recipient communications but does not delete data or cause permanent harm.
From the tool's definition Tool name 'disable_sequence' and description stating it 'Disable/freeze a sequence' and 'blocks new enrollments and holds current recipients' — this modifies the state of a sequence by freezing it, which is a reversible change.
Attacks that exploit this kind of access
The rule that runs disable_sequence 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 disable_sequence, this is the rule to start with:
disable_sequence stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 disable_sequence call is checked against it from then on.
Questions about disable_sequence
Disable/freeze a sequence. This blocks new enrollments and holds current recipients until the sequence is enabled again. To only stop new enrollments while current recipients continue, use pause_sequence_enrollments. It is categorised as a Write tool in the Sequenzy Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sequenzy MCP server in PolicyLayer and add a rule for disable_sequence: 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.
disable_sequence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disable_sequence 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 disable_sequence. 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.
disable_sequence 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.
This server
Across the catalogue