browser_network_requests
List HTTP requests the page made since open or last drain. Optional filters: method (GET/POST/...), url_pattern (regex), status_min (e.g. 400 for errors). Captures up to 200 most recent requests per page.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-network-requests.md
What browser_network_requests does on Dialogbrain
AI agents call browser_network_requests to retrieve information from Dialogbrain 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 |
|---|---|---|---|
clear | boolean | — | |
method | object | — | |
page_id | string | Yes | |
status_min | object | — | |
url_pattern | object | — |
Parameters from the server's own tool schema.
Why browser_network_requests is rated Low
This tool retrieves historical network request metadata from a page without triggering, modifying, or deleting any requests or data. It is a passive auditing/debugging function analogous to reading browser dev tools network logs. No side effects or state changes result from its use.
From the tool's definition Tool description states it 'List HTTP requests' with optional filters for method, URL pattern, and status codes.
Attacks that exploit this kind of access
The rule that runs browser_network_requests safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_network_requests, this is the rule to start with:
browser_network_requests 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 Dialogbrain, apply this rule, and every browser_network_requests call is checked against it from then on.
Questions about browser_network_requests
List HTTP requests the page made since open or last drain. Optional filters: method (GET/POST/...), url_pattern (regex), status_min (e.g. 400 for errors). Captures up to 200 most recent requests per page. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
browser_network_requests accepts 5 parameters: clear, method, page_id, status_min, url_pattern. Required: page_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for browser_network_requests: 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 Dialogbrain. Nothing to install.
browser_network_requests 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 browser_network_requests 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 browser_network_requests. 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.
browser_network_requests is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue