This record as markdown: /tools/nyxstrike/sublist3r.md
What sublist3r does on Nyxstrike
AI agents call sublist3r to retrieve information from Nyxstrike without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sublist3r is rated Low
Sublist3r is a widely known OSINT/reconnaissance tool that performs subdomain enumeration by querying public sources. It is a read/query operation with no direct system modification. However, on a penetration testing platform alongside offensive tools, it feeds attack workflows. Severity is medium because it enables target mapping that supports further attacks, though the tool itself only retrieves data.
From the tool's definition Tool name 'sublist3r' refers to the well-known subdomain enumeration tool Sublist3r, used for passive reconnaissance by discovering subdomains of a target domain. Description is empty.
Attacks that exploit this kind of access
The rule that runs sublist3r 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 sublist3r, this is the rule to start with:
sublist3r is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every sublist3r call is checked against it from then on.
Questions about sublist3r
sublist3r is a read tool on the Nyxstrike MCP server. It is categorised as a Read tool in the Nyxstrike MCP Server, which means it retrieves data without modifying state.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for sublist3r: 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.
sublist3r 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 sublist3r 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 sublist3r. 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.
sublist3r 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.
More on Nyxstrike, and thousands of servers like it.
This server
Across the catalogue