This record as markdown: /tools/browser/get-console-log.md
What get_console_log does on Browser
AI agents call get_console_log to retrieve information from Browser 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_log is rated Low
This tool retrieves console log data from a browser session. It performs a read-only query operation with no side effects, no code execution, and no data modification. The low severity reflects minimal risk even if misused—an AI could only gain visibility into logged debugging information, which has no destructive or operational impact.
From the tool's definition Tool name 'get_console_log' and description 'Get console log messages' indicate retrieval of existing console output with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_console_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Browser, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_console_log, this is the rule to start with:
get_console_log 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 Browser, apply this rule, and every get_console_log call is checked against it from then on.
Questions about get_console_log
Get console log messages. It is categorised as a Read tool in the Browser MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP server in PolicyLayer and add a rule for get_console_log: 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 Browser. Nothing to install.
get_console_log 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_log 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_log. 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_log is provided by the Browser MCP server (mcp-server-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Browser, and thousands of servers like it.
This server
Across the catalogue