get_recipient_suppression

Check whether one recipient is suppressed by Sequenzy

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/get-recipient-suppression.md

WHAT IT DOES

What get_recipient_suppression does on Sequenzy Mcp

AI agents call get_recipient_suppression 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 get_recipient_suppression is rated Low

This tool retrieves suppression status for a recipient—a read-only query operation. It has no side effects, does not modify data, and does not execute external operations. It falls clearly into the Read category with low severity since checking suppression status poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get_recipient_suppression' uses 'get' prefix; description states 'Check whether' indicating a query/lookup operation with no modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_recipient_suppression Allowed

get_recipient_suppression 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": {
    "get_recipient_suppression": {}
  }
}

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 get_recipient_suppression call is checked against it from then on.

FAQ

Questions about get_recipient_suppression

What does the get_recipient_suppression tool do? +

Check whether one recipient is suppressed by Sequenzy. 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 get_recipient_suppression? +

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

What risk level is get_recipient_suppression? +

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

Can I rate-limit get_recipient_suppression? +

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

How do I block get_recipient_suppression completely? +

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

What MCP server provides get_recipient_suppression? +

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

KEEP EXPLORING

More on Sequenzy, and thousands of servers like it.

This server

All 222 Sequenzy tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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