Get current JavaScript heap memory usage from the React Native app.
AI agents call get_memory_usage 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 memory statistics from a running React Native app with no side effects. It is purely informational/diagnostic, matching the Read category pattern (get, fetch, query). Memory inspection cannot alter application state or trigger unintended operations, resulting in low severity and high confidence.
From the tool's definition Tool name 'get_memory_usage' and description 'Get current JavaScript heap memory usage' indicate a query operation that retrieves diagnostic data without modifying or executing code. The verb 'get' and 'from' confirm data retrieval only.
Attacks that exploit this kind of access
Get current JavaScript heap memory usage from the React Native app. 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_memory_usage: 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_memory_usage 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_memory_usage 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_memory_usage. 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_memory_usage 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →