Generate one or more Burp Collaborator payloads.
AI agents invoke collaborator_generate 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.
Generating Burp Collaborator payloads triggers the creation of unique out-of-band interaction endpoints on Burp's external infrastructure. This is an active operation that initiates external resources/connections, going beyond a simple read. It enables SSRF/out-of-band testing probes, which can have external impact depending on how payloads are used.
From the tool's definition Generate one or more Burp Collaborator payloads
Documented attack patterns abuse exactly the kind of access collaborator_generate gives an agent:
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 collaborator_generate:
{
"version": "1",
"default": "deny",
"tools": {
"collaborator_generate": {
"limits": [
{
"counter": "collaborator_generate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}collaborator_generate 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.
Free to start. No card required.
Generate one or more Burp Collaborator payloads. 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.
Register the Burp Mcp Plus MCP server in PolicyLayer and add a rule for collaborator_generate: 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.
collaborator_generate 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 collaborator_generate 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 collaborator_generate. 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.
collaborator_generate 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.
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.