Check our browsers console errors
AI agents call getConsoleErrors 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 console error logs from the browser—passive monitoring with no capability to modify state, execute commands, or affect systems. It is purely observational. The sibling tools (getNetworkLogs, getSelectedElement, etc.) further confirm this server's focus on data capture rather than modification. Risk is low as misuse would only expose information already present in the console.
From the tool's definition Tool name 'getConsoleErrors' and description 'Check our browsers console errors' indicate data retrieval with no modification or side effects. Verb 'Check' and 'get' prefix confirm read-only access to existing console state.
Attacks that exploit this kind of access
Check our browsers console errors. 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 getConsoleErrors: 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.
getConsoleErrors 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 getConsoleErrors 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 getConsoleErrors. 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.
getConsoleErrors 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 →