list_campaign_events
List paginated raw email events for a campaign. Defaults to deliveries; use eventType or eventTypes to include opens, clicks, bounces, complaints, unsubscribes, sends, or delivery delays.
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/list-campaign-events.md
What list_campaign_events does on Sequenzy Mcp
AI agents call list_campaign_events to retrieve information from Sequenzy Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_campaign_events is rated Low
This tool queries and returns historical email campaign event data. It performs no modifications, deletions, or external operations—it only retrieves and filters existing event records. The paginated listing of events like opens, clicks, and bounces is purely informational and read-only.
From the tool's definition Tool description explicitly states 'List paginated raw email events' - the verb 'list' and the read-only nature of querying event data (deliveries, opens, clicks, bounces, etc.) confirm this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_campaign_events 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 list_campaign_events, this is the rule to start with:
list_campaign_events 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 Sequenzy Mcp, apply this rule, and every list_campaign_events call is checked against it from then on.
Questions about list_campaign_events
List paginated raw email events for a campaign. Defaults to deliveries; use eventType or eventTypes to include opens, clicks, bounces, complaints, unsubscribes, sends, or delivery delays. It is categorised as a Read tool in the Sequenzy Mcp MCP Server, which means it retrieves data without modifying state.
Register the Sequenzy MCP server in PolicyLayer and add a rule for list_campaign_events: 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.
list_campaign_events 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 list_campaign_events 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 list_campaign_events. 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.
list_campaign_events 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