bbot_scan

A execute tool on the Nyxstrike MCP server.

SERVERNyxstrike SOURCECommonHuman-Lab/nyxstrike

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nyxstrike/bbot-scan.md

WHAT IT DOES

What bbot_scan does on Nyxstrike

AI agents invoke bbot_scan to trigger actions in Nyxstrike. 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.

RISK

Why bbot_scan is rated High

BBOT (Bighuge BLS OSINT Tool) is a well-known automated reconnaissance and attack surface mapping tool. On an offensive security platform alongside tools like 'ai_reconnaissance_workflow' and 'ai_vulnerability_assessment', this tool almost certainly executes active scans against targets.

From the tool's definition Tool name 'bbot_scan' on a penetration testing platform; sibling tools include reconnaissance, vulnerability assessment, and attack suite generation tools.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bbot_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bbot_scan, this is the rule to start with:

bbot_scan Rate-limited

bbot_scan stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bbot_scan": {
      "limits": [
        {
          "counter": "bbot_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every bbot_scan call is checked against it from then on.

FAQ

Questions about bbot_scan

What does the bbot_scan tool do? +

bbot_scan is a execute tool on the Nyxstrike MCP server. It is categorised as a Execute tool in the Nyxstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bbot_scan? +

Register the Nyxstrike MCP server in PolicyLayer and add a rule for 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 Nyxstrike. Nothing to install.

What risk level is bbot_scan? +

bbot_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit bbot_scan? +

Yes. Add a rate_limit block to the 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.

How do I block bbot_scan completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides bbot_scan? +

bbot_scan is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nyxstrike, and thousands of servers like it.

This server

All 221 Nyxstrike tools → High-risk tools on this server →

Across the catalogue

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →