scan_wait

Block until an async scan job finishes or timeout_s elapses.

SERVERKali Security MCP SOURCEseac-25/kali-security-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/seac-25-kali-security-mcp/scan-wait.md

WHAT IT DOES

What scan_wait does on Kali Security MCP

AI agents invoke scan_wait to trigger actions in Kali Security MCP. 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_wait is rated High

Manages execution flow of security scan jobs in a penetration testing context.

From the tool's definition Block until an async scan job finishes or timeout_s elapses

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scan_wait safely

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

scan_wait Rate-limited

scan_wait 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_wait": {
      "limits": [
        {
          "counter": "scan_wait_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 Kali Security MCP, apply this rule, and every scan_wait call is checked against it from then on.

FAQ

Questions about scan_wait

What does the scan_wait tool do? +

Block until an async scan job finishes or timeout_s elapses. It is categorised as a Execute tool in the Kali Security MCP 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_wait? +

Register the Kali Security MCP server in PolicyLayer and add a rule for scan_wait: 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 Security MCP. Nothing to install.

What risk level is scan_wait? +

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

Can I rate-limit scan_wait? +

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

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

scan_wait is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Kali Security, and thousands of servers like it.

This server

All 194 Kali Security tools → High-risk tools on this server →

Across the catalogue

browser_wait_for_element on Percepta MCP Server →wait_for_renders on Why Did You Render →run_emba_scan on EMBA-MCP →qt_wait_for on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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