log_to_console · React Devtools MCP: Risk & Policy

WHAT IT DOES

What log_to_console does on React Devtools

AI agents invoke log_to_console to trigger actions in React 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.

WHY IT NEEDS A POLICY

Why log_to_console needs a policy

This tool triggers an external operation in the browser/app console environment, executing a logging action that sets the $r reference variable. While it appears read-like, it actively executes an operation in the target application's console context, potentially exposing internal component state and enabling further inspection or manipulation via $r in the console.

From the tool's definition Log an element to the browser/app console as $r

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_to_console Rate-limited

log_to_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": {
    "log_to_console": {
      "limits": [
        {
          "counter": "log_to_console_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches React Devtools, so you can run agents against it safely.

FAQ

Questions about log_to_console

What does the log_to_console tool do? +

Log an element to the browser/app console as $r. It is categorised as a Execute tool in the React 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 log_to_console? +

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

What risk level is log_to_console? +

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

Can I rate-limit log_to_console? +

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

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

log_to_console is provided by the React Devtools MCP server (skylarbarrera/react-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.