Get log entries for a scan.
AI agents call get_scan_log 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 historical log entries from a completed or ongoing scan. It has no side effects, does not modify data, does not execute code, and does not delete anything. The action is read-only and poses minimal risk if misused by an AI agent—at worst, it exposes log information that may contain reconnaissance data already collected by SpiderFoot, but retrieval alone cannot cause harm.
From the tool's definition Tool name 'get_scan_log' and description 'Get log entries for a scan' indicate retrieval of existing log data with no modification, deletion, or execution of operations. This is a pure query/fetch operation.
Attacks that exploit this kind of access
Get log entries for a scan. 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_scan_log: 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_scan_log 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_scan_log 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_scan_log. 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_scan_log 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 →