This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/delete-sequence.md
What delete_sequence does on Sequenzy Mcp
AI agents call delete_sequence 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 delete_sequence is rated Critical
Deleting a sequence in an email marketing automation system permanently removes the workflow, preventing future enrollments and potentially affecting dependent campaigns or subscriber journeys. This is irreversible and qualifies as Destructive.
From the tool's definition Tool name 'delete_sequence' and description 'Delete a sequence' explicitly indicate irreversible deletion of a sequence object, which cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_sequence, this is the rule to start with:
delete_sequence 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 delete_sequence call is checked against it from then on.
Questions about delete_sequence
Delete a sequence. 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 delete_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.
delete_sequence 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 delete_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 delete_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.
delete_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.
Across the catalogue