verify_sending_domain

SERVERSequenzy Mcp SOURCESequenzy/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/verify-sending-domain.md

WHAT IT DOES

What verify_sending_domain does on Sequenzy Mcp

AI agents invoke verify_sending_domain to trigger actions in Sequenzy Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why verify_sending_domain is rated High

Triggers an external DNS verification operation against a configured domain.

From the tool's definition Run a fresh DNS check for a configured sending domain

Attacks that exploit this kind of access

RECOMMENDED RULE

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

verify_sending_domain Rate-limited

verify_sending_domain stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_sending_domain": {
      "limits": [
        {
          "counter": "verify_sending_domain_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about verify_sending_domain

What does the verify_sending_domain tool do? +

Run a fresh DNS check for a configured sending domain and return DNS verification separately from sending readiness. A DNS-verified domain may still be activating; when readyToSend is false, read readiness.reason rather than the DKIM/SPF/MAIL FROM record statuses, which describe DNS only. It is categorised as a Execute tool in the Sequenzy Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on verify_sending_domain? +

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

verify_sending_domain is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit verify_sending_domain? +

Yes. Add a rate_limit block to the verify_sending_domain 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 verify_sending_domain completely? +

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

verify_sending_domain 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →