generate_sequence
[DEPRECATED compatibility alias - use create_sequence] Create and persist a disabled AI-generated email sequence draft from a goal. The saved draft appears in list_sequences. The name defaults to the goal and the trigger defaults to contact_added; optionally pass listId to scope it. Review before...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/generate-sequence.md
What generate_sequence does on Sequenzy Mcp
AI agents use generate_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 generate_sequence is rated Medium
This tool creates new email sequence data that is saved to the system and will appear in list_sequences, making it a Write operation. While marked deprecated, it still creates and stores data.
From the tool's definition Tool creates and persists a disabled email sequence draft, with description stating 'Create and persist a disabled AI-generated email sequence draft from a goal.
Attacks that exploit this kind of access
The rule that runs generate_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 generate_sequence, this is the rule to start with:
generate_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 generate_sequence call is checked against it from then on.
Questions about generate_sequence
[DEPRECATED compatibility alias - use create_sequence] Create and persist a disabled AI-generated email sequence draft from a goal. The saved draft appears in list_sequences. The name defaults to the goal and the trigger defaults to contact_added; optionally pass listId to scope it. Review before enabling. 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 generate_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.
generate_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 generate_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 generate_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.
generate_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