dns_recheck · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What dns_recheck does on TrekMail MCP Server

AI agents invoke dns_recheck to trigger actions in TrekMail MCP Server. 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 dns_recheck needs a policy

This tool triggers an external DNS verification process, which is an operation whose effects depend on arguments and cannot be classified as simple data retrieval (Read). It creates transient state (check IDs for polling) and initiates domain verification checks.

From the tool's definition Tool name 'dns_recheck' and description 'Trigger an asynchronous DNS verification check for a domain' indicates execution of an external operation (DNS verification).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dns_recheck Rate-limited

dns_recheck 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": {
    "dns_recheck": {
      "limits": [
        {
          "counter": "dns_recheck_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 TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about dns_recheck

What does the dns_recheck tool do? +

Trigger an asynchronous DNS verification check for a domain. Returns a check ID that can be polled with get_dns_check. It is categorised as a Execute tool in the TrekMail MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dns_recheck? +

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

What risk level is dns_recheck? +

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

Can I rate-limit dns_recheck? +

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

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

dns_recheck is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.