start_spiderfoot_web

What start_spiderfoot_web does on Pentester-MCP

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

Why start_spiderfoot_web is rated High

Spiderfoot performs active reconnaissance and information gathering by executing automated scanning operations. Starting the Spiderfoot web interface enables autonomous execution of reconnaissance workflows whose effects depend on target arguments provided. While primarily reconnaissance-oriented (Read-leaning), the 'start' verb and autonomous execution capability classify this as Execute rather than pure Read.

From the tool's definition Tool is part of Pentester-MCP server that 'enables AI assistants to autonomously execute over 200 open-source penetration testing tools'; Spiderfoot is a reconnaissance and OSINT framework that executes automated scanning and data gathering operations against…

The rule that runs start_spiderfoot_web safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_spiderfoot_web": {
      "limits": [
        {
          "counter": "start_spiderfoot_web_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about start_spiderfoot_web