AI agents use disable_spam_assassin 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.
Disabling SpamAssassin modifies the email filtering configuration by turning off spam protection. This is a reversible configuration change (it can be re-enabled), so it falls under Write rather than Destructive. However, misuse could expose the account to significant spam, making it medium severity.
From the tool's definition Disable SpamAssassin spam filtering
Documented attack patterns abuse exactly the kind of access disable_spam_assassin 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_spam_assassin:
{
"version": "1",
"default": "deny",
"tools": {
"disable_spam_assassin": {
"limits": [
{
"counter": "disable_spam_assassin_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disable_spam_assassin 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 SpamAssassin spam filtering. 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_spam_assassin: 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_spam_assassin 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_spam_assassin 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_spam_assassin. 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_spam_assassin 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.