Check our browser logs
AI agents call getConsoleLogs to retrieve information from BrowserTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves browser console logs for inspection and analysis purposes. It does not create, modify, delete, or execute any operations—it only reads and returns existing log data. The severity is low because console logs are typically non-sensitive diagnostic information, and retrieval poses minimal risk even if misused by an agent.
From the tool's definition Tool description states 'Check our browser logs' which is a retrieval operation with no modification or side effects. The sibling tools (getConsoleErrors, getNetworkErrors, getNetworkLogs, getSelectedElement) all follow a pattern of passive data inspection.
Attacks that exploit this kind of access
Check our browser logs. It is categorised as a Read tool in the BrowserTools MCP MCP Server, which means it retrieves data without modifying state.
Register the BrowserTools MCP server in PolicyLayer and add a rule for getConsoleLogs: 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 BrowserTools MCP. Nothing to install.
getConsoleLogs 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 getConsoleLogs 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 getConsoleLogs. 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.
getConsoleLogs is provided by the BrowserTools MCP server (sugatraj/cursor-browser-tools-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 →