browser_console_messages
Return console.log/warn/error events captured since the last drain. Filter by level ('log'|'info'|'warning'|'error'|'debug') and/or pattern (regex). Buffer caps at 500 entries; oldest are dropped first. Set clear=false to peek without draining.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-console-messages.md
What browser_console_messages does on Dialogbrain
AI agents call browser_console_messages to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
clear | boolean | — | |
level | object | — | |
page_id | string | Yes | |
pattern | object | — |
Parameters from the server's own tool schema.
Why browser_console_messages is rated Low
This tool reads captured browser console messages and optionally clears the buffer. It does not execute code, modify data, or trigger external operations. The primary action is retrieval/querying of already-captured log data, making it a Read category tool. Severity is low since it only exposes diagnostic/log information.
From the tool's definition 'Return console.log/warn/error events captured since the last drain' and 'Set clear=false to peek without draining' — the tool retrieves buffered log events with no side effects beyond optional buffer drain.
Attacks that exploit this kind of access
The rule that runs browser_console_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_console_messages, this is the rule to start with:
browser_console_messages 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 Dialogbrain, apply this rule, and every browser_console_messages call is checked against it from then on.
Questions about browser_console_messages
Return console.log/warn/error events captured since the last drain. Filter by level ('log'|'info'|'warning'|'error'|'debug') and/or pattern (regex). Buffer caps at 500 entries; oldest are dropped first. Set clear=false to peek without draining. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
browser_console_messages accepts 4 parameters: clear, level, page_id, pattern. Required: page_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain 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 Dialogbrain. 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 Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue