start_bbot_scan
AI agents invoke start_bbot_scan to trigger actions in BBOT MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool initiates external security scanning operations against specified targets. The effects (what gets scanned, what reconnaissance data is gathered) are entirely argument-dependent and cannot be predicted without seeing the parameters.
From the tool's definition start_bbot_scan is a tool to 'execute' reconnaissance scans (from server description: 'executing reconnaissance scans'). The tool name contains 'start' which initiates an external operation.
Attacks that exploit this kind of access
start_bbot_scan. It is categorised as a Execute tool in the BBOT MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BBOT MCP Server MCP server in PolicyLayer and add a rule for start_bbot_scan: 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.
start_bbot_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_bbot_scan 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 start_bbot_scan. 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.
start_bbot_scan 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 →