List captured network requests. Filter by url, method, status, since, limit.
AI agents call list_network_requests 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.
The tool retrieves and filters previously captured network request data. It performs no modifications, deletions, or external operations—purely informational querying of existing logs or monitoring data. The filtering parameters are all passive retrieval criteria, not write or execute operations.
From the tool's definition Tool name is 'list_network_requests' and description states 'List captured network requests' with filter options (url, method, status, since, limit). This is a retrieval/query operation with no side effects mentioned.
Attacks that exploit this kind of access
List captured network requests. Filter by url, method, status, 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 list_network_requests: 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.
list_network_requests 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 list_network_requests 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 list_network_requests. 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.
list_network_requests 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 →