Fetch persisted console logs for a browser session
AI agents call browser_get_console to retrieve information from AutoDev MCP 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 a browser session—a read-only operation that queries persisted data. It has no capability to modify, delete, or execute code. The verb 'fetch' confirms data retrieval semantics. While it accesses browser state information, this is non-sensitive diagnostic data typically used for debugging.
From the tool's definition Tool name 'browser_get_console' and description 'Fetch persisted console logs for a browser session' indicate retrieval of existing data without modification or side effects.
Attacks that exploit this kind of access
Fetch persisted console logs for a browser session. It is categorised as a Read tool in the AutoDev MCP MCP Server, which means it retrieves data without modifying state.
Register the AutoDev MCP server in PolicyLayer and add a rule for browser_get_console: 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 AutoDev MCP. Nothing to install.
browser_get_console 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 browser_get_console 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 browser_get_console. 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.
browser_get_console is provided by the AutoDev MCP server (rookiejefren/autocoding-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 →