Get summary of scans being tracked by this MCP server.
AI agents call get_active_scans_summary 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 and summarizes information about active scans. It has no side effects, does not modify data, does not execute external operations, and does not delete or move resources. It is a straightforward read operation that returns status information, making it the lowest severity category.
From the tool's definition Tool name 'get_active_scans_summary' and description 'Get summary of scans being tracked by this MCP server' indicate a retrieval operation that queries the current state of scans without modifying any data.
Attacks that exploit this kind of access
Get summary of scans being tracked by this MCP 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 get_active_scans_summary: 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.
get_active_scans_summary 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 get_active_scans_summary 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 get_active_scans_summary. 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.
get_active_scans_summary 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 →