High Risk →

dedup_to_repeater

Send a dedup entry to Burp Repeater, with optional structured overrides.

How to control dedup_to_repeater ↓

What dedup_to_repeater does on Burp Mcp Plus

AI agents invoke dedup_to_repeater to trigger actions in Burp Mcp Plus. 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.

High Risk

Why dedup_to_repeater needs a policy

This tool triggers an external operation in Burp Suite by sending an HTTP request entry to the Repeater tool, which queues it for replay/execution. It doesn't merely read or write data — it dispatches an action to an active security testing tool (Burp Repeater), which could be used to replay potentially malicious or sensitive HTTP requests against target systems.

From the tool's definition Send a dedup entry to Burp Repeater, with optional structured overrides

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

How to control dedup_to_repeater

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 dedup_to_repeater:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dedup_to_repeater": {
      "limits": [
        {
          "counter": "dedup_to_repeater_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Burp Mcp Plus — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about dedup_to_repeater

What does the dedup_to_repeater tool do? +

Send a dedup entry to Burp Repeater, with optional structured overrides. 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 dedup_to_repeater? +

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

What risk level is dedup_to_repeater? +

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

Can I rate-limit dedup_to_repeater? +

Yes. Add a rate_limit block to the dedup_to_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.

How do I block dedup_to_repeater completely? +

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

What MCP server provides dedup_to_repeater? +

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

Free to start. No card required.

20 Burp Mcp Plus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.