start_render_profile · React Native MCP: Risk & Policy

WHAT IT DOES

What start_render_profile does on React Native

AI agents invoke start_render_profile to trigger actions in React Native. 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_render_profile needs a policy

This tool executes an operation that instruments and modifies the runtime behavior of the React Native application by activating render profiling. While not destructive or modifying persistent data, it triggers external operations whose effects depend on the application state and subsequent profiling actions.

From the tool's definition Tool description states it 'Start[s] render profiling' which initiates a performance monitoring operation that instruments the React Native app runtime. This is an active operation that triggers code execution hooks within the application lifecycle.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_render_profile Rate-limited

start_render_profile 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_render_profile": {
      "limits": [
        {
          "counter": "start_render_profile_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 Native, so you can run agents against it safely.

FAQ

Questions about start_render_profile

What does the start_render_profile tool do? +

Start render profiling. Tracks mounts, re-renders, and unnecessary renders. It is categorised as a Execute tool in the React Native 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_render_profile? +

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

What risk level is start_render_profile? +

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

Can I rate-limit start_render_profile? +

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

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

start_render_profile is provided by the React Native MCP server (@ohah/react-native-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.