Exports HAR file with all network requests. Import into Chrome DevTools (F12 → Network → Import HAR).
AI agents call export_har to retrieve information from Browser-Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and exports captured network traffic data (HAR format) from the browser session. It only retrieves/collects existing data about network requests without modifying anything. However, severity is medium because HAR files can contain sensitive data including cookies, authentication headers, request/response bodies, and other credentials captured during the browser session.
From the tool's definition Exports HAR file with all network requests
Documented attack patterns abuse exactly the kind of access export_har gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser-Debugger, and nothing reaches the server without passing your rules. This is the rule we recommend for export_har:
{
"version": "1",
"default": "deny",
"tools": {
"export_har": {}
}
}export_har 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.
Exports HAR file with all network requests. Import into Chrome DevTools (F12 → Network → Import HAR). It is categorised as a Read tool in the Browser-Debugger MCP Server, which means it retrieves data without modifying state.
Register the Browser-Debugger MCP server in PolicyLayer and add a rule for export_har: 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 Browser-Debugger. Nothing to install.
export_har 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 export_har 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 export_har. 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.
export_har is provided by the Browser-Debugger MCP server (selvadinesh-giga/mcp-based-browser-debug-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browser-Debugger, 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.
14 Browser-Debugger tools catalogued and risk-classified — across an index of 43,000+ MCP servers.