Fetch persisted runtime error logs for a browser session
AI agents call browser_get_errors 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 reads and retrieves error logs from a persistent store without side effects. It performs a query operation to access existing logging data. No code execution, data modification, deletion, or financial operations are involved. The retrieval of error logs is necessary for debugging and testing workflows but carries minimal risk as it only exposes information about prior runtime events.
From the tool's definition Tool name 'browser_get_errors' and description 'Fetch persisted runtime error logs for a browser session' indicate data retrieval with no modification or execution of external operations.
Attacks that exploit this kind of access
Fetch persisted runtime error 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_errors: 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_errors 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_errors 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_errors. 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_errors 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 →