browser_network_requests
A read tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-network-requests.md
What browser_network_requests does on Looking Glass
AI agents call browser_network_requests to retrieve information from Looking Glass 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 | — | Clear requests after reading |
method | string | — | Filter by HTTP method (GET, POST, etc.) |
urlPattern | string | — | Filter by URL substring |
Parameters from the server's own tool schema.
Why browser_network_requests is rated Low
Network request inspection is a read-only operation that retrieves metadata about HTTP requests without side effects. The tool does not modify, execute, or delete data. While the empty description lowers confidence slightly, the naming pattern and context (AI-native browser for agents with self-healing and semantic extraction) indicates this retrieves historical or current network data for analysis.
From the tool's definition Tool name 'browser_network_requests' indicates retrieval of network request data. The description is empty, but the name and sibling tools (browser_analyze_page, browser_console_messages, browser_diagnose) suggest this is a monitoring/inspection function that…
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 Looking Glass, 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 Looking Glass, apply this rule, and every browser_network_requests call is checked against it from then on.
Questions about browser_network_requests
browser_network_requests is a read tool on the Looking Glass MCP server. It is categorised as a Read tool in the Looking Glass MCP Server, which means it retrieves data without modifying state.
browser_network_requests accepts 3 parameters: clear, method, urlPattern. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass 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 Looking Glass. 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 Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
This server
Across the catalogue