repeater_from_history

THE RISK

High Risk

Why repeater_from_history needs a policy

Based on the tool name and server context, this tool likely loads a historical HTTP request into Burp Suite's Repeater, which can then execute/replay HTTP requests against targets. The sibling tool 'dedup_to_repeater' confirms the pattern of sending requests to Repeater. This constitutes an Execute-level action as it triggers external HTTP operations. Confidence is reduced due to empty description.

From the tool's definition Tool name 'repeater_from_history' and server context 'Burp Suite integration' with sibling tools like 'dedup_to_repeater' and 'intruder_from_history' suggest sending HTTP requests via Burp Suite's Repeater tool

Documented attack patterns abuse exactly the kind of access repeater_from_history gives an agent:

POLICY

How to control repeater_from_history

PolicyLayer is an MCP gateway — it sits between your AI agents and Burp Mcp Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for repeater_from_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "repeater_from_history": {
      "limits": [
        {
          "counter": "repeater_from_history_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

repeater_from_history 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.

Create a free account and register Burp Mcp Plus — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Burp Mcp Plus tools

Execute intruder_from_history intruder_from_history Execute repeater_from_template repeater_from_template Execute collaborator_generate Generate one or more Burp Collaborator payloads. Execute dedup_to_repeater Send a dedup entry to Burp Repeater, with optional structured overrides. Execute send_request send_request Read sitemap Build a sitemap from Burp proxy history (no upstream Target tool exists). Read collaborator_check Poll Burp Collaborator for received interactions. Read dedup_get Fetch a dedup entry by its 1-based index.

All 20 Burp Mcp Plus tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Burp Mcp Plus → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about repeater_from_history

What does the repeater_from_history tool do? +

repeater_from_history. It is categorised as a Execute tool in the Burp Mcp Plus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on repeater_from_history? +

Register the Burp Mcp Plus MCP server in PolicyLayer and add a rule for repeater_from_history: 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 Burp Mcp Plus. Nothing to install.

What risk level is repeater_from_history? +

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

Can I rate-limit repeater_from_history? +

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

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

repeater_from_history is provided by the Burp Mcp Plus MCP server (titaniumtushar/burp-mcp-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Burp Mcp Plus tool call.

Start from Burp Mcp Plus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →