AI agents call get_console_logs to retrieve information from Yandex Browser 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 the browser for monitoring and debugging purposes. It is purely a read operation that queries existing data (console messages) without creating, modifying, deleting, or executing anything. The blast radius is minimal as it only accesses diagnostic information that an agent would already be able to see through normal browser operation.
From the tool's definition Tool name 'get_console_logs' and description 'Retrieve browser console logs' indicate reading/querying browser console output without modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_console_logs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yandex Browser MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_console_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_console_logs": {}
}
}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.
Получить логи консоли браузера. It is categorised as a Read tool in the Yandex Browser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yandex Browser MCP Server MCP server in PolicyLayer and add a rule for 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 Yandex Browser MCP Server. Nothing to install.
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 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 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.
get_console_logs is provided by the Yandex Browser MCP Server MCP server (t1trit/yandex-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Yandex Browser MCP Server, 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.
18 Yandex Browser MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.