http_intruder
Simple Intruder (sniper) fuzzing. Iterates payloads over each param individually.
This record as markdown: /tools/nyxstrike/http-intruder.md
What http_intruder does on Nyxstrike
AI agents invoke http_intruder 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.
Why http_intruder is rated High
This tool performs active fuzzing/intrusion attacks against HTTP parameters by iterating payloads, which constitutes executing external operations against a target system. It is part of an offensive security/penetration testing platform, increasing blast radius. While it doesn't inherently delete data, it executes attack sequences against potentially live systems, warranting high severity.
From the tool's definition 'Simple Intruder (sniper) fuzzing. Iterates payloads over each param individually' — actively sends attack payloads against target HTTP parameters
Attacks that exploit this kind of access
The rule that runs http_intruder 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 http_intruder, this is the rule to start with:
http_intruder 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every http_intruder call is checked against it from then on.
Questions about http_intruder
Simple Intruder (sniper) fuzzing. Iterates payloads over each param individually. 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.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for http_intruder: 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.
http_intruder 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 http_intruder 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 http_intruder. 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.
http_intruder 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.
Across the catalogue