MCP connection status. appConnected, devices list (deviceId, platform). Call first to see connected devices.
AI agents call get_debugger_status to retrieve information from React Native without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and reports state information about debugger connections and available devices. It has no side effects, cannot modify data, execute code, or affect system state. The capability to see device listings is standard diagnostic functionality with minimal security risk. Confidence is high because the description clearly indicates a read-only status/list operation.
From the tool's definition Tool retrieves MCP connection status and lists connected devices (deviceId, platform). No modification, deletion, or execution implied. Purely informational query operation.
Attacks that exploit this kind of access
MCP connection status. appConnected, devices list (deviceId, platform). Call first to see connected devices. It is categorised as a Read tool in the React Native MCP Server, which means it retrieves data without modifying state.
Register the React Native MCP server in PolicyLayer and add a rule for get_debugger_status: 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.
get_debugger_status 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_debugger_status 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_debugger_status. 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_debugger_status 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.
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 →