AI agents use disable_dkim to create or update resources in cPanel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your cPanel MCP Server environment.
This tool modifies email security configuration (DKIM settings) for a domain, making it a Write operation. It is reversible (DKIM can be re-enabled), so it is not Destructive. Severity is high because disabling DKIM weakens email authentication and can facilitate email spoofing or phishing attacks against the domain, affecting email deliverability and security posture.
From the tool's definition Tool is named 'disable_dkim' and described as 'Disable DKIM for a domain'. DKIM is a DNS/email authentication record. Disabling it modifies the email authentication configuration for a domain, which is reversible by re-enabling DKIM.
Documented attack patterns abuse exactly the kind of access disable_dkim gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and cPanel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for disable_dkim:
{
"version": "1",
"default": "deny",
"tools": {
"disable_dkim": {
"limits": [
{
"counter": "disable_dkim_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disable_dkim 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.
Free to start. No card required.
Disable DKIM for a domain. It is categorised as a Write tool in the cPanel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for disable_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 cPanel MCP Server. Nothing to install.
disable_dkim is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disable_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.
Set action: deny in the PolicyLayer policy for disable_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.
disable_dkim is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from cPanel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
164 cPanel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.