view_source · React Devtools MCP: Risk & Policy

WHAT IT DOES

What view_source does on React Devtools

AI agents invoke view_source 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 view_source needs a policy

This tool executes an external action by opening source code in an IDE, which is an operation that affects the external environment. It doesn't merely read data but triggers a side effect in the developer's toolchain. Misuse could open arbitrary files in the IDE, hence medium severity.

From the tool's definition 'Open element source in IDE' — triggers an external operation (opening a file in the IDE environment)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

view_source Rate-limited

view_source 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": {
    "view_source": {
      "limits": [
        {
          "counter": "view_source_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 view_source

What does the view_source tool do? +

Open element source in IDE (if supported). 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 view_source? +

Register the React Devtools MCP server in PolicyLayer and add a rule for view_source: 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 view_source? +

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

Can I rate-limit view_source? +

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

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

view_source 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.