browser_network_requests
AI agents call browser_network_requests to retrieve information from Playwright MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name implies reading/querying network traffic or request logs, which is a read operation. However, the description is empty, so confidence is lowered. If it merely lists captured requests, it's Read with medium severity since network data can contain sensitive information like auth tokens or cookies. No indication of side effects.
From the tool's definition Tool name 'browser_network_requests' suggests retrieving/listing network request data captured by the browser.
Attacks that exploit this kind of access
browser_network_requests. It is categorised as a Read tool in the Playwright MCP MCP Server, which means it retrieves data without modifying state.
Register the Playwright 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 Playwright MCP. 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 Playwright MCP server (naumana3services-maker/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 →