AI agents call get_console_logs to retrieve information from Chrome Debug 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 historical console output from a Chrome debugging session. It is a pure query operation that reads data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an AI agent could only exfiltrate information already present in console logs, which may contain sensitive data but does not alter system state.
From the tool's definition Tool name is 'get_console_logs' and description states 'Get console logs from Chrome' — retrieves already-generated log data with no side effects or modifications.
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 Chrome Debug 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.
Get console logs from Chrome. It is categorised as a Read tool in the Chrome Debug MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome Debug 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 Chrome Debug 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 Chrome Debug MCP Server MCP server (robertheadley/chrome-debug-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Chrome Debug MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Chrome Debug MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.