scan_clam

Scan with ClamAV

SERVER1Panel MCP Server SOURCEeaveluo/1panel-mcp

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/eaveluo-1panel-mcp/scan-clam.md

WHAT IT DOES

What scan_clam does on 1Panel MCP Server

AI agents invoke scan_clam to trigger actions in 1Panel 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 scan_clam is rated High

Running a ClamAV scan executes an external process/operation on the server. It doesn't merely read data passively; it actively invokes a scanning engine that traverses the filesystem and may quarantine or flag files. This is an Execute-category action. Severity is medium because misuse (e.g., scanning large directories repeatedly) could consume significant CPU/IO resources, though it doesn't directly destroy data.

From the tool's definition 'Scan with ClamAV' — triggers an external antivirus scanning operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scan_clam safely

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

scan_clam Rate-limited

scan_clam 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": {
    "scan_clam": {
      "limits": [
        {
          "counter": "scan_clam_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 1Panel MCP Server, apply this rule, and every scan_clam call is checked against it from then on.

FAQ

Questions about scan_clam

What does the scan_clam tool do? +

Scan with ClamAV. It is categorised as a Execute tool in the 1Panel 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 scan_clam? +

Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for scan_clam: 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 1Panel MCP Server. Nothing to install.

What risk level is scan_clam? +

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

Can I rate-limit scan_clam? +

Yes. Add a rate_limit block to the scan_clam 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 scan_clam completely? +

Set action: deny in the PolicyLayer policy for scan_clam. 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 scan_clam? +

scan_clam is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 286 1Panel MCP Server tools → High-risk tools on this server →

Across the catalogue

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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