Add network mock. Matching XHR/fetch return mock without hitting network.
AI agents invoke set_network_mock 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.
This tool intercepts network requests and substitutes mock responses, which is an active runtime manipulation. It doesn't merely read data or write persistent data, but executes an interception layer that changes how the application behaves. Misuse could cause the app to receive falsified data, leading to incorrect application states or misleading test results.
From the tool's definition Matching XHR/fetch return mock without hitting network — intercepts and overrides network requests, altering runtime behavior of the app
Attacks that exploit this kind of access
Add network mock. Matching XHR/fetch return mock without hitting network. 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.
Register the React Native MCP server in PolicyLayer and add a rule for set_network_mock: 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.
set_network_mock is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_network_mock 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 set_network_mock. 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.
set_network_mock 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 →