Check ALL our network logs
AI agents call getNetworkLogs to retrieve information from BrowserTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries network log data from a browser, which is a read-only operation with no side effects on the system. However, severity is medium rather than low because network logs may contain sensitive information (API keys, authentication tokens, personal data in request/response bodies, user behavior patterns) that could be exploited if an AI agent misuses this data or exfiltrates it.
From the tool's definition Tool name 'getNetworkLogs' and description 'Check ALL our network logs' indicate retrieval/querying of existing network activity data with no modification capability.
Attacks that exploit this kind of access
Check ALL our network logs. It is categorised as a Read tool in the BrowserTools MCP MCP Server, which means it retrieves data without modifying state.
Register the BrowserTools MCP server in PolicyLayer and add a rule for getNetworkLogs: 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 BrowserTools MCP. Nothing to install.
getNetworkLogs 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 getNetworkLogs 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 getNetworkLogs. 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.
getNetworkLogs is provided by the BrowserTools MCP server (sugatraj/cursor-browser-tools-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 →