list_console_messages
List all console messages for the currently selected page since the last navigation.
This record as markdown: /tools/anirbandz-chrome-mcp-devtool/list-console-messages.md
What list_console_messages does on Chrome DevTools MCP
AI agents call list_console_messages to retrieve information from Chrome DevTools MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_console_messages is rated Low
This tool queries and retrieves console messages from a browser page—a read-only operation that does not modify state, execute code, or affect system behavior. It is informational only, similar to viewing browser developer tools output. The blast radius is minimal since console messages are typically non-sensitive debugging data, though in some contexts they could contain logs with minor information disclosure risk.
From the tool's definition Tool name 'list_console_messages' and description 'List all console messages for the currently selected page since the last navigation' indicate retrieval of existing data with no side effects.
Attacks that exploit this kind of access
The rule that runs list_console_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome DevTools MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_console_messages, this is the rule to start with:
list_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 Chrome DevTools MCP, apply this rule, and every list_console_messages call is checked against it from then on.
Questions about list_console_messages
List all console messages for the currently selected page since the last navigation. It is categorised as a Read tool in the Chrome DevTools MCP MCP Server, which means it retrieves data without modifying state.
Register the Chrome DevTools MCP server in PolicyLayer and add a rule for list_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 Chrome DevTools MCP. Nothing to install.
list_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 list_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 list_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.
list_console_messages is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome DevTools, and thousands of servers like it.
This server
Across the catalogue