Get console messages from the browser
AI agents call get_console_messages to retrieve information from Browser MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves browser console data (logs, warnings, errors) for inspection and analysis. It performs a read-only query of existing console state without modifying data, executing code, or triggering side effects. The low severity reflects minimal blast radius—an agent cannot cause harm by reading console messages.
From the tool's definition Tool name 'get_console_messages' and description 'Get console messages from the browser' indicate a retrieval operation with no side effects. Console messages are diagnostic output and logs.
Attacks that exploit this kind of access
Get console messages from the browser. It is categorised as a Read tool in the Browser MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP Bridge MCP server in PolicyLayer and add a rule for get_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 MCP Bridge. Nothing to install.
get_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 get_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 get_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.
get_console_messages is provided by the Browser MCP Bridge MCP server (robhicks/browser-mcp-bridge). 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 →