List all scans on the SpiderFoot server.
AI agents call list_scans to retrieve information from SpiderFoot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about existing scans from the SpiderFoot server. It performs a query operation with no capability to modify, delete, or execute external actions. The blast radius of misuse is minimal—an AI agent could only enumerate scans to gather reconnaissance information, which is low-risk in the context of an OSINT platform designed for investigation workflows.
From the tool's definition Tool name 'list_scans' and description 'List all scans on the SpiderFoot server' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all scans on the SpiderFoot server. It is categorised as a Read tool in the SpiderFoot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SpiderFoot MCP Server MCP server in PolicyLayer and add a rule for list_scans: 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.
list_scans is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_scans 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 list_scans. 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.
list_scans 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →