AI agents call browser_get_console_logs to retrieve information from YetiBrowser MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves console log output from the browser—a read-only operation that queries state without altering it, creating resources, executing code, or causing destructive changes. Even in a browser automation context, retrieving logs poses minimal risk as logs are informational artifacts.
From the tool's definition Tool name 'browser_get_console_logs' and description 'Get the console logs from the browser' indicate retrieval of existing data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access browser_get_console_logs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and YetiBrowser MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_get_console_logs:
{
"version": "1",
"default": "deny",
"tools": {
"browser_get_console_logs": {}
}
}browser_get_console_logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the console logs from the browser. It is categorised as a Read tool in the YetiBrowser MCP MCP Server, which means it retrieves data without modifying state.
Register the YetiBrowser MCP server in PolicyLayer and add a rule for browser_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 YetiBrowser MCP. Nothing to install.
browser_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 browser_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 browser_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.
browser_get_console_logs is provided by the YetiBrowser MCP server (yetidevworks/yetibrowser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from YetiBrowser MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 YetiBrowser MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.