Search Burp proxy history with a regex; returns a compact list of
AI agents call search_history to retrieve information from Burp Mcp Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing proxy history data using a regex pattern and returns results. It has no side effects, does not modify data, execute code, delete records, or affect financial state. It is purely a read operation on stored HTTP request/response history within Burp Suite. The low severity reflects minimal blast radius—an agent could only retrieve sensitive data already captured in local proxy logs.
From the tool's definition Tool name is 'search_history' and description states it 'Search[es] Burp proxy history with a regex; returns a compact list of' — the verb 'search' and 'returns' indicate data retrieval with no modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access search_history 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 search_history:
{
"version": "1",
"default": "deny",
"tools": {
"search_history": {}
}
}search_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Burp proxy history with a regex; returns a compact list of. It is categorised as a Read tool in the Burp Mcp Plus MCP Server, which means it retrieves data without modifying state.
Register the Burp Mcp Plus MCP server in PolicyLayer and add a rule for search_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.
search_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_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.
Set action: deny in the PolicyLayer policy for search_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.
search_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.
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.