enable_sender_domain_inbound · Run402 MCP: Risk & Policy

WHAT IT DOES

What enable_sender_domain_inbound does on Run402

AI agents use enable_sender_domain_inbound to create or update resources in Run402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Run402 environment.

WHY IT NEEDS A POLICY

Why enable_sender_domain_inbound needs a policy

This tool creates or modifies email infrastructure settings reversibly. While it changes system state (enables email routing), the change is not destructive—it can be disabled, and no data is deleted or overwritten. The manual DNS update requirement and reliance on DKIM verification mean the modification is somewhat controlled.

From the tool's definition Tool modifies email routing configuration by enabling inbound email on a custom domain and returns MX records for DNS update. Description explicitly states 'Enable inbound email' and 'route through run402', indicating configuration of email delivery system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enable_sender_domain_inbound Rate-limited

enable_sender_domain_inbound stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "enable_sender_domain_inbound": {
      "limits": [
        {
          "counter": "enable_sender_domain_inbound_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about enable_sender_domain_inbound

What does the enable_sender_domain_inbound tool do? +

Enable inbound email on a verified custom sender domain. Replies to <slug>@<your-domain> will route through run402. Requires DKIM-verified domain. Returns the MX record to add to DNS. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on enable_sender_domain_inbound? +

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

What risk level is enable_sender_domain_inbound? +

enable_sender_domain_inbound is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit enable_sender_domain_inbound? +

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

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

enable_sender_domain_inbound is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.