export_har
Export captured entries as a HAR 1.2 log. Optionally scope by device, host, and date range.
This record as markdown: /tools/dev-busymate-busymate-devtools/export-har.md
What export_har does on Busymate DevTools
AI agents call export_har to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
host | string | — | |
limit | number | — | |
since | string | — | |
before | string | — | |
deviceName | string | — | |
device_uuid | string | — |
Parameters from the server's own tool schema.
Why export_har is rated Low
The tool reads and exports previously captured network traffic data (HAR format). It performs no modifications or deletions — it retrieves and formats existing entries. Severity is medium because HAR logs can contain sensitive data such as authentication tokens, cookies, request/response bodies, and API keys captured from HTTPS traffic across multiple devices.
From the tool's definition Export captured entries as a HAR 1.2 log. Optionally scope by device, host, and date range.
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs export_har safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_har, this is the rule to start with:
export_har is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Busymate DevTools, apply this rule, and every export_har call is checked against it from then on.
Questions about export_har
Export captured entries as a HAR 1.2 log. Optionally scope by device, host, and date range. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
export_har accepts 6 parameters: host, limit, since, before, deviceName, device_uuid. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools 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 Busymate DevTools. 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 Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue