Get the status of a specific scan
AI agents call get_scan_status to retrieve information from BBOT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns the current status of an ongoing or completed scan. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It is purely informational in nature, making it a Read category tool with low severity risk. Even if misused by an AI agent, it cannot cause harm beyond potentially accessing status information about existing scans.
From the tool's definition Tool name 'get_scan_status' and description 'Get the status of a specific scan' indicate a query operation that retrieves state information without modifying or executing operations. This is a read-only information retrieval function.
Attacks that exploit this kind of access
Get the status of a specific scan. It is categorised as a Read tool in the BBOT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BBOT MCP Server MCP server in PolicyLayer and add a rule for get_scan_status: 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 BBOT MCP Server. Nothing to install.
get_scan_status 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_status 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_status. 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_status is provided by the BBOT MCP Server MCP server (marlinkcyber/bbot-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 →