Start a ClamAV virus scan on a directory (requires ClamAV plugin on server)
AI agents invoke start_virus_scan 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.
This tool triggers execution of a virus scanner on server directories. While not destructive or financial, it runs an external operation (ClamAV) whose effects depend on the directory argument and scan results. The scan could identify security issues, impact system performance, or generate resource-intensive operations.
From the tool's definition Tool name 'start_virus_scan' and description 'Start a ClamAV virus scan on a directory' indicate execution of an external scanning operation (ClamAV) triggered by the tool.
Documented attack patterns abuse exactly the kind of access start_virus_scan 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 start_virus_scan:
{
"version": "1",
"default": "deny",
"tools": {
"start_virus_scan": {
"limits": [
{
"counter": "start_virus_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} start_virus_scan 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.
Start a ClamAV virus scan on a directory (requires ClamAV plugin on server). 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 start_virus_scan: 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.
start_virus_scan 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 start_virus_scan 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 start_virus_scan. 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.
start_virus_scan 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.