List recent Burp proxy history entries with their history_index.
AI agents call list_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 and retrieves proxy history metadata (entries and their indices) from Burp Suite without modifying, executing, or deleting anything. It has minimal security impact—an agent could only gather information about past HTTP traffic visible to Burp, which is already captured by the proxy. No side effects, no code execution, no data destruction.
From the tool's definition Tool description states 'List recent Burp proxy history entries' — a retrieval operation with no modification or execution capability. The verb 'list' and the passive retrieval of historical data confirm read-only semantics.
Documented attack patterns abuse exactly the kind of access list_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 list_history:
{
"version": "1",
"default": "deny",
"tools": {
"list_history": {}
}
}list_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.
List recent Burp proxy history entries with their history_index. 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 list_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.
list_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 list_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 list_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.
list_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.