Low Risk

check_deliverability

Check email deliverability for a domain — SPF, DKIM, DMARC, MX, BIMI.

Part of the Emailens MCP server.

check_deliverability is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE EMAILENS MCP →

Free to start. No card required.

AI agents call check_deliverability to retrieve information from Emailens MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though check_deliverability only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_deliverability": {}
  }
}

See the full Emailens MCP policy for all 7 tools.

Get this rule live on your own Emailens MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY EMAILENS MCP →

These attack patterns abuse exactly the kind of access check_deliverability gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so check_deliverability only ever does what you allow.

SECURE EMAILENS MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the check_deliverability tool do? +

Check email deliverability for a domain — SPF, DKIM, DMARC, MX, BIMI.. It is categorised as a Read tool in the Emailens MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_deliverability? +

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

What risk level is check_deliverability? +

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

Can I rate-limit check_deliverability? +

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

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

check_deliverability is provided by the Emailens MCP server (https://emailens.dev/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Emailens MCP tool call.

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

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.