List console messages buffered since the browser was launched. Types: log, info, warning, error, debug, etc.
AI agents call interceptor_browser_list_console to retrieve information from Proxy 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 logs from a browser session. It queries existing data (console message buffer) without creating, modifying, deleting, or executing any operations. The capability to read console output for debugging or analysis purposes poses minimal security risk on its own, as it is passive observation.
From the tool's definition Tool description: 'List console messages buffered since the browser was launched.' The verb 'list' and the action of retrieving already-emitted console messages indicates data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access interceptor_browser_list_console gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for interceptor_browser_list_console:
{
"version": "1",
"default": "deny",
"tools": {
"interceptor_browser_list_console": {}
}
}interceptor_browser_list_console 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.
List console messages buffered since the browser was launched. Types: log, info, warning, error, debug, etc. It is categorised as a Read tool in the Proxy MCP Server, which means it retrieves data without modifying state.
Register the Proxy MCP server in PolicyLayer and add a rule for interceptor_browser_list_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 Proxy. Nothing to install.
interceptor_browser_list_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 interceptor_browser_list_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 interceptor_browser_list_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.
interceptor_browser_list_console is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proxy, 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.
89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.