retry_domain_dkim · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What retry_domain_dkim does on TrekMail MCP Server

AI agents invoke retry_domain_dkim 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 retry_domain_dkim needs a policy

This tool triggers DKIM key regeneration, which executes an operation whose outcome depends on domain and system state. DKIM provisioning involves generating new cryptographic keys and updating DNS records—operations that cannot be undone without explicit administrative action.

From the tool's definition Tool name 'retry_domain_dkim' and description 'Restart DKIM key provisioning for a domain' indicates triggering a cryptographic regeneration operation with external effects (DNS record updates).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retry_domain_dkim Rate-limited

retry_domain_dkim 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": {
    "retry_domain_dkim": {
      "limits": [
        {
          "counter": "retry_domain_dkim_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 retry_domain_dkim

What does the retry_domain_dkim tool do? +

Restart DKIM key provisioning for a domain. Use this if DKIM provisioning failed or needs to be regenerated. 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 retry_domain_dkim? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for retry_domain_dkim: 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 retry_domain_dkim? +

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

Can I rate-limit retry_domain_dkim? +

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

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

retry_domain_dkim 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.