start_scan · SpiderFoot MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_scan does on SpiderFoot MCP Server

AI agents invoke start_scan 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 start_scan needs a policy

This tool initiates active OSINT scanning operations against targets, which is an Execute action—it runs reconnaissance tasks with external side effects. While not directly destructive or financial, it can trigger significant network activity, resource consumption, and data collection that could be abused to scan unauthorized targets or systems.

From the tool's definition Tool is named 'start_scan' on a SpiderFoot OSINT scanning server. SpiderFoot performs reconnaissance and investigation workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_scan Rate-limited

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

FAQ

Questions about start_scan

What does the start_scan tool do? +

start_scan. 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 start_scan? +

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

What risk level is start_scan? +

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

Can I rate-limit start_scan? +

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

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

start_scan 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.