Get network requests
AI agents call browser_network_requests to retrieve information from Browser Pool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical or current network request data from a browser session without modifying, executing, or deleting anything. It is purely observational and diagnostic in nature, consistent with Read category tools like 'list' or 'fetch'. The blast radius of misuse is minimal—an agent could observe network traffic but cannot manipulate it or cause harm through inspection alone.
From the tool's definition Tool name 'browser_network_requests' and description 'Get network requests' indicate data retrieval with no modification. The verb 'Get' confirms read-only semantics. No side effects or state changes result from querying network request logs.
Attacks that exploit this kind of access
Get network requests. It is categorised as a Read tool in the Browser Pool MCP Server, which means it retrieves data without modifying state.
Register the Browser Pool 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 Browser Pool. 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 Browser Pool MCP server (omgeverdo/browser-pool-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →