start_profiling · React Devtools MCP: Risk & Policy

WHAT IT DOES

What start_profiling does on React Devtools

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

Profiling is an active operation that triggers code execution within the React application's runtime to collect performance metrics. While it does not permanently modify data (making it not Destructive) or retrieve static information (making it not Read), it actively initiates a monitoring process whose effects depend on what the application does during profiling. This constitutes an Execute action.

From the tool's definition Tool name 'start_profiling' and description 'Start profiling React renders' indicate initiation of a profiling operation that actively modifies the runtime state of a React application by enabling performance monitoring.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_profiling Rate-limited

start_profiling 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": {
    "start_profiling": {
      "limits": [
        {
          "counter": "start_profiling_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 start_profiling

What does the start_profiling tool do? +

Start profiling React renders. 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 start_profiling? +

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

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

Can I rate-limit start_profiling? +

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

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

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