Disable ModSecurity (WAF) for all domains
AI agents invoke disable_modsecurity 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 (Web Application Firewall) for all domains removes active security protection across the entire hosting environment. This is an operational/configuration change that triggers an external security state change — it doesn't delete data but executes a system-wide configuration action.
From the tool's definition Disable ModSecurity (WAF) for all domains
Documented attack patterns abuse exactly the kind of access disable_modsecurity 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:
{
"version": "1",
"default": "deny",
"tools": {
"disable_modsecurity": {
"limits": [
{
"counter": "disable_modsecurity_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}disable_modsecurity 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 (WAF) for all 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: 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 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 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. 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 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.