Get browser console logs
AI agents call get_console_logs to retrieve information from Chromium ARM64 Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves diagnostic information (console logs) from the browser runtime. It performs a read-only query with no side effects, no data modification, no code execution, and no destructive actions. The logs are already generated by the browser and the tool simply fetches them for inspection. This is a typical diagnostic/observability operation with minimal security risk.
From the tool's definition Tool name is 'get_console_logs' and description states 'Get browser console logs' — retrieves console output without modifying state.
Attacks that exploit this kind of access
Get browser console logs. It is categorised as a Read tool in the Chromium ARM64 Browser MCP Server, which means it retrieves data without modifying state.
Register the Chromium ARM64 Browser 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 Chromium ARM64 Browser. 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 Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). 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 →