request_malware_scan

Request a new malware scan for a hosting package

SERVER20i MCP Server SOURCEcbrown35/20i-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/cbrown35-20i-mcp/request-malware-scan.md

WHAT IT DOES

What request_malware_scan does on 20i MCP Server

AI agents invoke request_malware_scan to trigger actions in 20i 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 request_malware_scan is rated High

This tool initiates an active malware scan process on a hosting package, which is an external operation with real-world effects (resource consumption, scanning activity). It does not merely read existing data but triggers a new execution. It is not destructive, financial, or a simple write, so Execute is the most appropriate category.

From the tool's definition 'Request a new malware scan' — triggers an external scanning operation on a hosting package

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs request_malware_scan safely

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

request_malware_scan Rate-limited

request_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": {
    "request_malware_scan": {
      "limits": [
        {
          "counter": "request_malware_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 20i MCP Server, apply this rule, and every request_malware_scan call is checked against it from then on.

FAQ

Questions about request_malware_scan

What does the request_malware_scan tool do? +

Request a new malware scan for a hosting package. It is categorised as a Execute tool in the 20i 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 request_malware_scan? +

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

What risk level is request_malware_scan? +

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

Can I rate-limit request_malware_scan? +

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

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

request_malware_scan is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 302 20i MCP Server tools → High-risk tools on this server →

Across the catalogue

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

Guides

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