AI agents invoke clamav_scan to trigger actions in Kali. 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.
The tool executes ClamAV (an antivirus scanner) with user-provided parameters. While ClamAV is primarily a read/scan tool, 'execute with provided parameters' on a Kali Linux pentesting server means arbitrary command arguments can be passed, which could include options that modify files, quarantine or delete detected files, or scan sensitive paths.
From the tool's definition 'Execute clamav with the provided parameters' — runs an external antivirus/malware scanning tool with arbitrary parameters on a Kali Linux MCP server
Attacks that exploit this kind of access
Execute clamav with the provided parameters. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP server in PolicyLayer and add a rule for clamav_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 Kali. Nothing to install.
clamav_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 clamav_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 clamav_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.
clamav_scan is provided by the Kali MCP server (pentestt00ls/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →