get_console_message
Gets a console message by its ID. You can get all messages by calling ${listConsoleMessages.name}.
This record as markdown: /tools/anirbandz-chrome-mcp-devtool/get-console-message.md
What get_console_message does on Chrome DevTools MCP
AI agents call get_console_message 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 get_console_message is rated Low
This is a read-only operation that queries and retrieves console messages from a Chrome DevTools session. It has no capability to modify browser state, execute code, delete data, or trigger financial transactions. The lowest blast radius applies—returning console messages cannot harm the system or cause unintended side effects.
From the tool's definition Tool name 'get_console_message' and description 'Gets a console message by its ID' indicate retrieval of data with no side effects. Retrieves already-captured console output.
Attacks that exploit this kind of access
The rule that runs get_console_message 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 get_console_message, this is the rule to start with:
get_console_message 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 get_console_message call is checked against it from then on.
Questions about get_console_message
Gets a console message by its ID. You can get all messages by calling ${listConsoleMessages.name}. 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 get_console_message: 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.
get_console_message 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_message 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_message. 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_message 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