autorecon_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/autorecon-scan.md

WHAT IT DOES

What autorecon_scan does on Nyxstrike

AI agents invoke autorecon_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 autorecon_scan is rated High

AutoRecon is a well-known automated multi-threaded network reconnaissance tool used in penetration testing that executes active scanning and enumeration against target systems. Even though the description is empty, the tool name strongly implies active network scanning execution.

From the tool's definition Tool name 'autorecon_scan' on a penetration testing platform server ('AI Powered penetration testing Platform for offensive security research'); sibling tools include reconnaissance, payload generation, and attack suite tools.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs autorecon_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 autorecon_scan, this is the rule to start with:

autorecon_scan Rate-limited

autorecon_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": {
    "autorecon_scan": {
      "limits": [
        {
          "counter": "autorecon_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 autorecon_scan call is checked against it from then on.

FAQ

Questions about autorecon_scan

What does the autorecon_scan tool do? +

autorecon_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 autorecon_scan? +

Register the Nyxstrike MCP server in PolicyLayer and add a rule for autorecon_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 autorecon_scan? +

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

Can I rate-limit autorecon_scan? +

Yes. Add a rate_limit block to the autorecon_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 autorecon_scan completely? +

Set action: deny in the PolicyLayer policy for autorecon_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 autorecon_scan? +

autorecon_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 →