get_console_debug

Get console debug messages

SERVERBrowser SOURCEmcp-server-browser

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/browser/get-console-debug.md

WHAT IT DOES

What get_console_debug does on Browser

AI agents call get_console_debug to retrieve information from Browser without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_console_debug is rated Low

This tool queries and returns debug messages from the browser console. It performs a read-only operation that does not modify, execute, or delete any data. The retrieval of console logs is a standard debugging operation with minimal security impact unless sensitive data is exposed through those logs, but the tool itself is purely informational.

From the tool's definition Tool name is 'get_console_debug' and description states 'Get console debug messages' — this retrieves existing console output with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_console_debug safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Browser, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_console_debug, this is the rule to start with:

get_console_debug Allowed

get_console_debug is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_console_debug": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Browser, apply this rule, and every get_console_debug call is checked against it from then on.

FAQ

Questions about get_console_debug

What does the get_console_debug tool do? +

Get console debug messages. It is categorised as a Read tool in the Browser MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_console_debug? +

Register the Browser MCP server in PolicyLayer and add a rule for get_console_debug: 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 Browser. Nothing to install.

What risk level is get_console_debug? +

get_console_debug is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_console_debug? +

Yes. Add a rate_limit block to the get_console_debug 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.

How do I block get_console_debug completely? +

Set action: deny in the PolicyLayer policy for get_console_debug. 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.

What MCP server provides get_console_debug? +

get_console_debug is provided by the Browser MCP server (mcp-server-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Browser, and thousands of servers like it.

This server

All 19 Browser tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →