Search across scan results.
AI agents call search_scan_results 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 performs a search query on existing scan data, which is a read-only operation. It retrieves information without modifying, executing, or deleting anything. While the server itself enables reconnaissance activities, this specific tool only reads pre-existing scan results. Low severity because querying data has minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name is 'search_scan_results' and description states 'Search across scan results' - a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
Search across scan results. 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 search_scan_results: 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.
search_scan_results 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 search_scan_results 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 search_scan_results. 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.
search_scan_results 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 →