Get console
AI agents call browser_console_messages 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 console messages (logs, warnings, errors) from an active browser session. It is purely observational with no side effects, no code execution, and no state modifications. It falls squarely into the Read category. The minimal description is somewhat uninformative but the name clearly indicates retrieval of existing console data.
From the tool's definition Tool name and description: 'Get console' - retrieves console output/messages from a browser session without modifying state or triggering actions.
Attacks that exploit this kind of access
Get console. 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_console_messages: 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_console_messages 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_console_messages 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_console_messages. 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_console_messages 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.
browser_console_messages is one line of Browser Pool's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →