Profile CPU usage for a given duration and return the hottest functions sorted by self time.
AI agents call get_cpu_profile to retrieve information from Mcp Rn Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves performance profiling metrics from a running React Native app. It collects and reads CPU usage statistics but does not execute arbitrary code, modify application state, delete data, or commit financial transactions. It is purely observational/diagnostic in nature, consistent with the sibling tools on this server (get_console_logs, get_errors, get_memory_usage, etc.) which are all Read category.
From the tool's definition Tool name is 'get_cpu_profile' and description states it returns profiling data about CPU usage and function hotspots. The verb 'get' and 'return' indicate data retrieval with no modification or execution of external operations.
Attacks that exploit this kind of access
Profile CPU usage for a given duration and return the hottest functions sorted by self time. It is categorised as a Read tool in the Mcp Rn Devtools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Rn Devtools MCP server in PolicyLayer and add a rule for get_cpu_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 Mcp Rn Devtools. Nothing to install.
get_cpu_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_cpu_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.
Set action: deny in the PolicyLayer policy for get_cpu_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.
get_cpu_profile is provided by the Mcp Rn Devtools MCP server (pablonortiz/mcp-rn-devtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_cpu_profile is one line of Mcp Rn Devtools's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →