获取浏览器控制台日志
AI agents call get_console_logs to retrieve information from MCP Browser Logger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and retrieves console log data from the browser via Chrome DevTools Protocol. It performs a passive query operation with no capability to modify, delete, execute, or trigger external operations. The retrieval of logs is a non-destructive read-only operation, placing it squarely in the Read category with minimal security risk.
From the tool's definition Tool name 'get_console_logs' and description 'retrieves browser console logs'. The Chinese description '获取浏览器控制台日志' translates to 'get browser console logs', confirming it retrieves/queries existing log data with no modification or side effects.
Attacks that exploit this kind of access
获取浏览器控制台日志. It is categorised as a Read tool in the MCP Browser Logger MCP Server, which means it retrieves data without modifying state.
Register the MCP Browser Logger 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 MCP Browser Logger. 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 MCP Browser Logger MCP server (tao-lionel/mcp-browser-logger). 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 →