list_email_sends

SERVERSequenzy Mcp SOURCESequenzy/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/list-email-sends.md

WHAT IT DOES

What list_email_sends does on Sequenzy Mcp

AI agents call list_email_sends 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.

RISK

Why list_email_sends is rated Low

Tool retrieves and queries email delivery records with no modification or destructive capability.

From the tool's definition List and filter recent sent-email delivery history; search, filter, retrieve timestamps.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_email_sends 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_email_sends, this is the rule to start with:

list_email_sends Allowed

list_email_sends is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_email_sends": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every list_email_sends call is checked against it from then on.

FAQ

Questions about list_email_sends

What does the list_email_sends tool do? +

List and filter the recent sent-email delivery history shown in the dashboard. Search subject/title or recipient, filter by delivery status, email type, bounce type, or source ID, then pass a returned emailSendId to get_email_send for exact open/click timestamps and the complete event timeline. Each row carries recipientEmail, subscriberId, automationNodeId, abTestVariantId, and sent/delivered/opened/clicked timestamps, so rows join into a recipient-level delivery matrix without re-reading the raw event stream. Pass automationNodeId to list only the recipients of one sequence step. Delivery rows are retained for 14 days, so this is the wrong tool for send totals: read get_sequence_stats steps[] or list_email_metrics, which cover the full retained event window. It is categorised as a Read tool in the Sequenzy Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_email_sends? +

Register the Sequenzy MCP server in PolicyLayer and add a rule for list_email_sends: 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.

What risk level is list_email_sends? +

list_email_sends is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_email_sends? +

Yes. Add a rate_limit block to the list_email_sends 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.

How do I block list_email_sends completely? +

Set action: deny in the PolicyLayer policy for list_email_sends. 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.

What MCP server provides list_email_sends? +

list_email_sends 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.

KEEP EXPLORING

More on Sequenzy, and thousands of servers like it.

This server

All 222 Sequenzy tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →