impacket_run

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/impacket-run.md

WHAT IT DOES

What impacket_run does on Nyxstrike

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

Impacket is commonly used in offensive security to execute remote code, exploit vulnerabilities, and perform lateral movement attacks. The 'run' suffix indicates execution of potentially arbitrary operations. Given the penetration testing platform context and offensive security sibling tools, this tool has critical blast radius—misuse could compromise systems, steal credentials, or escalate privileges.

From the tool's definition Tool name 'impacket_run' combined with server context (penetration testing platform) and sibling tools (payload generation, attack suites, vulnerability assessment).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

impacket_run Rate-limited

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

FAQ

Questions about impacket_run

What does the impacket_run tool do? +

impacket_run 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 impacket_run? +

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

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

Can I rate-limit impacket_run? +

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

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

impacket_run 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

shortcuts_run on Apple Apps MCP →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 →