browser_console

Return recent browser console messages with secrets redacted

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/browser-console.md

WHAT IT DOES

What browser_console does on CoWork OS

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

RISK

Why browser_console is rated Low

The tool only retrieves/reads existing browser console messages and applies redaction for safety. It has no side effects — it does not execute code, modify state, or trigger external operations. The secrets redaction further limits exposure. Severity is low because it only surfaces already-logged console output.

From the tool's definition Return recent browser console messages with secrets redacted

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_console safely

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

browser_console Allowed

browser_console 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": {
    "browser_console": {}
  }
}

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

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

FAQ

Questions about browser_console

What does the browser_console tool do? +

Return recent browser console messages with secrets redacted. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_console? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for browser_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 CoWork OS. Nothing to install.

What risk level is browser_console? +

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

Can I rate-limit browser_console? +

Yes. Add a rate_limit block to the browser_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 browser_console completely? +

Set action: deny in the PolicyLayer policy for browser_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 browser_console? +

browser_console is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

browser_extract_text on Percepta MCP Server → The MCP Attack Database →

Guides

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