clear_console

Clear the browser console. Returns: Status of the clear operation

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/benjaminr-chrome-devtools-mcp/clear-console.md

WHAT IT DOES

What clear_console does on Chrome Devtools

AI agents invoke clear_console to trigger actions in Chrome Devtools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why clear_console is rated High

Clearing the browser console is a browser action executed via CDP. It has no persistent data impact but does irreversibly remove console log history for the session. Since this is a browser operation (not data deletion in a storage sense) and the effect is minor, Execute is the most appropriate category. Severity is low as console logs are ephemeral and this has minimal blast radius.

From the tool's definition 'Clear the browser console' - triggers an external browser operation via Chrome DevTools Protocol

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_console safely

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

clear_console Rate-limited

clear_console stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clear_console": {
      "limits": [
        {
          "counter": "clear_console_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about clear_console

What does the clear_console tool do? +

Clear the browser console. Returns: Status of the clear operation. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on clear_console? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for clear_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 Chrome Devtools. Nothing to install.

What risk level is clear_console? +

clear_console is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit clear_console? +

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

How do I block clear_console completely? +

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

What MCP server provides clear_console? +

clear_console is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 47 Chrome Devtools tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →