resend_verify_domain · Integrations MCP: Risk & Policy

WHAT IT DOES

What resend_verify_domain does on Integrations MCP

AI agents invoke resend_verify_domain to trigger actions in Integrations 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.

WHY IT NEEDS A POLICY

Why resend_verify_domain needs a policy

The tool name suggests it triggers a domain verification process via the Resend email service. This is an external operation (triggering verification, likely sending a verification request or checking DNS records), which falls under Execute. Without a description, confidence is low. Severity is medium as misuse could affect domain/email configuration but is not directly destructive or financial.

From the tool's definition Tool name: resend_verify_domain; description is empty or uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resend_verify_domain Rate-limited

resend_verify_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": {
    "resend_verify_domain": {
      "limits": [
        {
          "counter": "resend_verify_domain_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Integrations MCP, so you can run agents against it safely.

FAQ

Questions about resend_verify_domain

What does the resend_verify_domain tool do? +

resend_verify_domain. It is categorised as a Execute tool in the Integrations 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 resend_verify_domain? +

Register the Integrations MCP server in PolicyLayer and add a rule for resend_verify_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 Integrations MCP. Nothing to install.

What risk level is resend_verify_domain? +

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

Can I rate-limit resend_verify_domain? +

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

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

resend_verify_domain is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.