zernio_list_sequences
List all message sequences (drip campaigns) for automated follow-up messaging.
This record as markdown: /tools/eyalm321-zernio-mcp/zernio-list-sequences.md
What zernio_list_sequences does on Zernio
AI agents call zernio_list_sequences to retrieve information from Zernio without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why zernio_list_sequences is rated Low
This tool queries and returns existing drip campaign sequences without triggering, modifying, or deleting them. It is a straightforward read operation on campaign metadata. The blast radius of misuse is minimal; an attacker could learn about existing campaigns but cannot execute, modify, or harm them.
From the tool's definition Tool name contains 'list' and description states 'List all message sequences' — a pure retrieval operation with no modification, deletion, or execution of campaigns.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs zernio_list_sequences safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zernio, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zernio_list_sequences, this is the rule to start with:
zernio_list_sequences is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zernio, apply this rule, and every zernio_list_sequences call is checked against it from then on.
Questions about zernio_list_sequences
List all message sequences (drip campaigns) for automated follow-up messaging. It is categorised as a Read tool in the Zernio MCP Server, which means it retrieves data without modifying state.
Register the Zernio MCP server in PolicyLayer and add a rule for zernio_list_sequences: 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 Zernio. Nothing to install.
zernio_list_sequences is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zernio_list_sequences 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 zernio_list_sequences. 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.
zernio_list_sequences is provided by the Zernio MCP server (eyalm321/zernio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zernio, and thousands of servers like it.
This server
Across the catalogue