List captured state changes. Filter by component, since, limit.
AI agents call get_state_changes 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 retrieves and lists previously captured state changes from a React Native application's monitoring system. It performs read-only queries with optional filters but does not modify, delete, execute code, or affect application state. The low severity reflects minimal security risk—an agent could only access debugging information about past state transitions.
From the tool's definition Tool description states 'List captured state changes' with filtering capabilities (component, since, limit). The verb 'List' and filtering on historical data indicates retrieval/query operation with no side effects.
Attacks that exploit this kind of access
List captured state changes. Filter by component, since, limit. 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_state_changes: 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_state_changes 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_state_changes 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_state_changes. 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_state_changes 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 →