http_repeater
Send a crafted request (Burp Repeater equivalent). request_spec keys: url, method, headers, cookies, data.
This record as markdown: /tools/hexstrike-ai/http-repeater.md
What http_repeater does on Hexstrike Ai
AI agents invoke http_repeater to trigger actions in Hexstrike Ai. 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_repeater is rated High
This tool sends arbitrary crafted HTTP requests to external targets, functioning as a Burp Suite Repeater equivalent. It triggers external network operations with user-controlled parameters (URL, method, headers, cookies, body data), making it an Execute-category tool. In an offensive security context, misuse could involve sending malicious payloads to arbitrary targets, making the blast radius high.
From the tool's definition Send a crafted request (Burp Repeater equivalent). request_spec keys: url, method, headers, cookies, data.
Attacks that exploit this kind of access
The rule that runs http_repeater safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hexstrike Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For http_repeater, this is the rule to start with:
http_repeater 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 Hexstrike Ai, apply this rule, and every http_repeater call is checked against it from then on.
Questions about http_repeater
Send a crafted request (Burp Repeater equivalent). request_spec keys: url, method, headers, cookies, data. It is categorised as a Execute tool in the Hexstrike Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hexstrike Ai MCP server in PolicyLayer and add a rule for http_repeater: 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 Hexstrike Ai. Nothing to install.
http_repeater 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_repeater 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_repeater. 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_repeater is provided by the Hexstrike Ai MCP server (0x4m4/hexstrike-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hexstrike Ai, and thousands of servers like it.
Across the catalogue