list_recipient_suppressions
List the recipients this company cannot reach: protected global invalid-recipient suppressions for addresses associated with the company, protected workspace hard bounces without conclusive invalid-inbox evidence, removable workspace soft-bounce escalations, and protected spam complaints. Each ro...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/list-recipient-suppressions.md
What list_recipient_suppressions does on Sequenzy Mcp
AI agents call list_recipient_suppressions 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_recipient_suppressions is rated Low
Tool retrieves suppression records without modifying data or triggering external operations.
From the tool's definition List the recipients, suppressions, protected global invalid-recipient, hard bounces, soft-bounce, spam complaints.
Attacks that exploit this kind of access
The rule that runs list_recipient_suppressions 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_recipient_suppressions, this is the rule to start with:
list_recipient_suppressions 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_recipient_suppressions call is checked against it from then on.
Questions about list_recipient_suppressions
List the recipients this company cannot reach: protected global invalid-recipient suppressions for addresses associated with the company, protected workspace hard bounces without conclusive invalid-inbox evidence, removable workspace soft-bounce escalations, and protected spam complaints. Each row includes a stable suppressionType, and the response echoes the applied sortBy/sortOrder. Sort by. 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_recipient_suppressions: 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_recipient_suppressions 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_recipient_suppressions 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_recipient_suppressions. 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_recipient_suppressions 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