spiderfoot
Execute SpiderFoot for OSINT automation with enhanced logging.
This record as markdown: /tools/nyxstrike/spiderfoot.md
What spiderfoot does on Nyxstrike
AI agents invoke spiderfoot to trigger actions in Nyxstrike. 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 spiderfoot is rated High
SpiderFoot is a legitimate OSINT automation tool that executes reconnaissance and information-gathering operations against specified targets. While not inherently destructive or financial, it performs active external operations whose effects (network reconnaissance, target profiling, information collection) depend on the arguments provided (target, modules, scope). This fits the Execute category.
From the tool's definition Tool name 'spiderfoot' combined with description 'Execute SpiderFoot for OSINT automation with enhanced logging' — the verb 'Execute' and the nature of SpiderFoot (an open-source OSINT reconnaissance framework that runs automated scans and probes against…
Attacks that exploit this kind of access
The rule that runs spiderfoot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spiderfoot, this is the rule to start with:
spiderfoot 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every spiderfoot call is checked against it from then on.
Questions about spiderfoot
Execute SpiderFoot for OSINT automation with enhanced logging. It is categorised as a Execute tool in the Nyxstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for spiderfoot: 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 Nyxstrike. Nothing to install.
spiderfoot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the spiderfoot 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.
Set action: deny in the PolicyLayer policy for spiderfoot. 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.
spiderfoot is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
Across the catalogue