Gets a console message by its ID. You can get all messages by calling ${listConsoleMessages.name}.
AI agents call get_console_message to retrieve information from Chrome Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves console message data from a running Chrome browser session. It has no capability to modify, delete, or trigger external operations. The worst case misuse would be information disclosure of console logs, which is a low-severity read-only concern. It aligns with the 'fetch' pattern of the Read category.
From the tool's definition Tool retrieves console messages by ID without modifying, deleting, or executing any code. The description explicitly states it 'gets' a message, which is a read operation. No side effects are mentioned or implied.
Attacks that exploit this kind of access
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 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. 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 (nimbus21/chrome-devtools-mcp). 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 →