run_malware_scan · Sentinel MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_malware_scan does on Sentinel MCP Server

AI agents invoke run_malware_scan to trigger actions in Sentinel 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.

WHY IT NEEDS A POLICY

Why run_malware_scan needs a policy

This tool triggers execution of ClamAV malware scanning engine, which performs file/binary analysis and pattern matching against malware signatures. While the scan itself is defensive in intent, it executes external code/processes whose behavior depends on scan targets and configuration—files scanned could be affected, and scan results inform downstream actions.

From the tool's definition Tool name 'run_malware_scan' and description 'Run Malware scan using ClamAV' indicate execution of an external security scanning tool (ClamAV) on files or systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_malware_scan Rate-limited

run_malware_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": {
    "run_malware_scan": {
      "limits": [
        {
          "counter": "run_malware_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sentinel MCP Server, so you can run agents against it safely.

FAQ

Questions about run_malware_scan

What does the run_malware_scan tool do? +

Run Malware scan using ClamAV. It is categorised as a Execute tool in the Sentinel 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 run_malware_scan? +

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

What risk level is run_malware_scan? +

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

Can I rate-limit run_malware_scan? +

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

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

run_malware_scan is provided by the Sentinel MCP Server MCP server (pranjal-lnct/scurity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.