Low Risk

get-domain

Get a domain by ID from Resend. Returns full domain details including DNS records needed for verification.

How to control get-domain ↓

AI agents call get-domain to retrieve information from Email Sending MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and returns domain information (DNS records, verification details) from the Resend API. It performs a query operation that does not create, modify, delete, or execute any actions—it only reads and returns data.

From the tool's definition Tool name 'get-domain' and description 'Get a domain by ID from Resend. Returns full domain details including DNS records needed for verification.' indicate retrieval of existing domain configuration data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get-domain gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Email Sending MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get-domain:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-domain": {}
  }
}

get-domain is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Email Sending MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get-domain tool do? +

Get a domain by ID from Resend. Returns full domain details including DNS records needed for verification. It is categorised as a Read tool in the Email Sending MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-domain? +

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

What risk level is get-domain? +

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

Can I rate-limit get-domain? +

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

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

get-domain is provided by the Email Sending MCP server (resend/resend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Email Sending MCP tool call.

Deterministic rules across all 77 Email Sending MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

77 Email Sending MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.