remove_recipient_suppression
Remove a workspace-scoped soft-bounce escalation for an exact recipient associated with the company, then reactivate bounced company subscribers. Global invalid-recipient, workspace hard-bounce, Amazon SES account-level, complaint, and unsubscribe suppressions are protected.
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/remove-recipient-suppression.md
What remove_recipient_suppression does on Sequenzy Mcp
AI agents use remove_recipient_suppression to create or update resources in Sequenzy Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sequenzy Mcp environment.
Why remove_recipient_suppression is rated Medium
Reversibly removes suppression and reactivates subscribers, potentially enabling emails to problematic addresses.
From the tool's definition Remove suppression, reactivate bounced company subscribers
Attacks that exploit this kind of access
The rule that runs remove_recipient_suppression 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 remove_recipient_suppression, this is the rule to start with:
remove_recipient_suppression stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 remove_recipient_suppression call is checked against it from then on.
Questions about remove_recipient_suppression
Remove a workspace-scoped soft-bounce escalation for an exact recipient associated with the company, then reactivate bounced company subscribers. Global invalid-recipient, workspace hard-bounce, Amazon SES account-level, complaint, and unsubscribe suppressions are protected. It is categorised as a Write tool in the Sequenzy Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sequenzy MCP server in PolicyLayer and add a rule for remove_recipient_suppression: 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.
remove_recipient_suppression is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the remove_recipient_suppression 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 remove_recipient_suppression. 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.
remove_recipient_suppression 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