wait_for_scan_completion · SpiderFoot MCP Server MCP

WHAT IT DOES

What wait_for_scan_completion does on SpiderFoot MCP Server

AI agents invoke wait_for_scan_completion to trigger actions in SpiderFoot 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 wait_for_scan_completion needs a policy

Although the name suggests a passive wait operation, it functions within SpiderFoot's scanning workflow which involves executing reconnaissance and investigation operations. Waiting for scan completion is part of an Execute flow (run_query, execute_script, trigger external operations).

From the tool's definition Tool name 'wait_for_scan_completion' indicates it monitors or waits for an asynchronous operation (SpiderFoot OSINT scan) to finish. The description is empty, limiting direct evidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_for_scan_completion Rate-limited

wait_for_scan_completion 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": {
    "wait_for_scan_completion": {
      "limits": [
        {
          "counter": "wait_for_scan_completion_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 SpiderFoot MCP Server, so you can run agents against it safely.

FAQ

Questions about wait_for_scan_completion

What does the wait_for_scan_completion tool do? +

wait_for_scan_completion. It is categorised as a Execute tool in the SpiderFoot 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 wait_for_scan_completion? +

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

What risk level is wait_for_scan_completion? +

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

Can I rate-limit wait_for_scan_completion? +

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

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

wait_for_scan_completion is provided by the SpiderFoot MCP Server MCP server (marlinkcyber/spiderfoot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.