start_virus_scan

Start a ClamAV virus scan on a directory (requires ClamAV plugin on server)

SERVERcPanel MCP Server SOURCE0xhayd3n/cpanel-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xhayd3n-cpanel-mcp-server/start-virus-scan.md

WHAT IT DOES

What start_virus_scan does on cPanel MCP 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.

RISK

Why start_virus_scan is rated High

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_virus_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and cPanel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_virus_scan, this is the rule to start with:

start_virus_scan Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_virus_scan": {
      "limits": [
        {
          "counter": "start_virus_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect cPanel MCP Server, apply this rule, and every start_virus_scan call is checked against it from then on.

FAQ

Questions about start_virus_scan

What does the start_virus_scan tool do? +

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.

How do I enforce a policy on start_virus_scan? +

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.

What risk level is start_virus_scan? +

start_virus_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_virus_scan? +

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.

How do I block start_virus_scan completely? +

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.

What MCP server provides start_virus_scan? +

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.

KEEP EXPLORING

More on cPanel MCP Server, and thousands of servers like it.

This server

All 164 cPanel MCP Server tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →run_emba_scan on EMBA-MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →