list_transactional_emails
List transactional email templates with subjects, delivery metrics, API slugs, and dashboard URLs. Each item also carries
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/list-transactional-emails.md
What list_transactional_emails does on Sequenzy Mcp
AI agents call list_transactional_emails 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_transactional_emails is rated Low
Retrieves metadata about email templates without modifying or executing any operations.
From the tool's definition List transactional email templates with subjects, delivery metrics, API slugs, and dashboard URLs.
Attacks that exploit this kind of access
The rule that runs list_transactional_emails 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_transactional_emails, this is the rule to start with:
list_transactional_emails 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_transactional_emails call is checked against it from then on.
Questions about list_transactional_emails
List transactional email templates with subjects, delivery metrics, API slugs, and dashboard URLs. Each item also carries. 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_transactional_emails: 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_transactional_emails 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_transactional_emails 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_transactional_emails. 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_transactional_emails 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