Get browser console logs with filtering options. Returns logs from web applications running on localhost.
AI agents call get_browser_logs to retrieve information from DevTools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves console logs from browser applications running on localhost. It is purely informational, querying existing log data with optional filters. There are no side effects, no code execution, no data modification, and no destructive operations.
From the tool's definition Tool description states 'Get browser console logs' - a retrieval operation with no modification or deletion. The word 'Get' and the absence of any action verbs like 'delete', 'modify', 'execute', or 'clear' indicate a read-only operation.
Attacks that exploit this kind of access
Get browser console logs with filtering options. Returns logs from web applications running on localhost. It is categorised as a Read tool in the DevTools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevTools MCP Server MCP server in PolicyLayer and add a rule for get_browser_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 DevTools MCP Server. Nothing to install.
get_browser_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_browser_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_browser_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_browser_logs is provided by the DevTools MCP Server MCP server (shabaraba/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 →