This record as markdown: /tools/browser/get-console-error.md
What get_console_error does on Browser
AI agents call get_console_error to retrieve information from Browser without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_console_error is rated Low
This tool retrieves diagnostic/debug information (console error logs) with no side effects. It is a passive read operation that queries existing console state without executing code, modifying data, or triggering external operations. The context of sibling tools (execute_script, close_tab) that perform actual browser automation reinforces that this tool is informational only.
From the tool's definition Tool name 'get_console_error' and description 'Get console error messages' indicate retrieval of already-logged error data from browser console; no modification, deletion, or code execution involved.
Attacks that exploit this kind of access
The rule that runs get_console_error safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Browser, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_console_error, this is the rule to start with:
get_console_error 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 Browser, apply this rule, and every get_console_error call is checked against it from then on.
Questions about get_console_error
Get console error messages. It is categorised as a Read tool in the Browser MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP server in PolicyLayer and add a rule for get_console_error: 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. Nothing to install.
get_console_error 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 get_console_error 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 get_console_error. 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.
get_console_error is provided by the Browser MCP server (mcp-server-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Browser, and thousands of servers like it.
This server
Across the catalogue