Disable ModSecurity for specific domains
AI agents invoke disable_modsecurity_domain to trigger actions in cPanel 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.
Disabling ModSecurity removes active web application firewall protection for a domain, exposing it to attacks. This is an operational/security configuration change that triggers an external security subsystem change. It is reversible (can be re-enabled), so it's Execute rather than Destructive, but the blast radius is high because it removes a security layer that could allow exploitation of vulnerabilities.
From the tool's definition Disable ModSecurity for specific domains
Documented attack patterns abuse exactly the kind of access disable_modsecurity_domain 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_modsecurity_domain:
{
"version": "1",
"default": "deny",
"tools": {
"disable_modsecurity_domain": {
"limits": [
{
"counter": "disable_modsecurity_domain_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} disable_modsecurity_domain 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.
Free to start. No card required.
Disable ModSecurity for specific domains. It is categorised as a Execute tool in the cPanel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for disable_modsecurity_domain: 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_modsecurity_domain is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the disable_modsecurity_domain 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_modsecurity_domain. 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_modsecurity_domain 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.