get_console_logs
Get browser console logs with optional filtering. Args: level: Filter by log level (log, warn, error, info, debug) limit: Maximum number of logs to return Returns: List of console logs matching the criteria
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-console-logs.md
What get_console_logs does on Chrome Devtools
AI agents call get_console_logs to retrieve information from Chrome Devtools 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_logs is rated Low
This tool only queries and returns existing console log data without any side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because accessing console logs poses minimal risk—logs are typically diagnostic information already present in the browser session, and misuse would only expose information, not cause damage or…
From the tool's definition Tool retrieves console logs with optional filtering by level and limit parameters. Description explicitly states it 'Get browser console logs' with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_console_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_console_logs, this is the rule to start with:
get_console_logs 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, apply this rule, and every get_console_logs call is checked against it from then on.
Questions about get_console_logs
Get browser console logs with optional filtering. Args: level: Filter by log level (log, warn, error, info, debug) limit: Maximum number of logs to return Returns: List of console logs matching the criteria. 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_logs: 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_logs 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_logs 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_logs. 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_logs is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). 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