virus_scan_site
Start a virus/malware scan on a website (checks for web shells, malicious code, trojans).
This record as markdown: /tools/aapanel-mcp/virus-scan-site.md
What virus_scan_site does on Aapanel
AI agents invoke virus_scan_site to trigger actions in Aapanel. 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.
Why virus_scan_site is rated High
This tool triggers an active scan operation on a website — an external operation with real-world effects (CPU/IO usage, potential quarantine actions). It initiates a process rather than merely reading data, placing it in Execute. Severity is medium since misuse could disrupt site performance or trigger false-positive quarantine actions, but it is not inherently destructive or financial.
From the tool's definition Start a virus/malware scan on a website (checks for web shells, malicious code, trojans)
Attacks that exploit this kind of access
The rule that runs virus_scan_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For virus_scan_site, this is the rule to start with:
virus_scan_site 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every virus_scan_site call is checked against it from then on.
Questions about virus_scan_site
Start a virus/malware scan on a website (checks for web shells, malicious code, trojans). It is categorised as a Execute tool in the Aapanel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aapanel MCP server in PolicyLayer and add a rule for virus_scan_site: 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 Aapanel. Nothing to install.
virus_scan_site 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 virus_scan_site 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 virus_scan_site. 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.
virus_scan_site is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue