http_set_rules
Set match/replace rules used to rewrite parts of URL/query/headers/body before sending.
This record as markdown: /tools/nyxstrike/http-set-rules.md
What http_set_rules does on Nyxstrike
AI agents invoke http_set_rules 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_set_rules is rated High
This tool modifies HTTP requests in-flight by rewriting URLs, query parameters, headers, and body content before transmission. On an offensive security/penetration testing platform, this enables active manipulation of outbound HTTP traffic — a form of request interception and tampering that constitutes execution of external operations.
From the tool's definition Set match/replace rules used to rewrite parts of URL/query/headers/body before sending
Attacks that exploit this kind of access
The rule that runs http_set_rules 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_set_rules, this is the rule to start with:
http_set_rules 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_set_rules call is checked against it from then on.
Questions about http_set_rules
Set match/replace rules used to rewrite parts of URL/query/headers/body before sending. 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_set_rules: 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_set_rules 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_set_rules 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_set_rules. 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_set_rules 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