AI agents call get_elements_by_test_id to retrieve information from Rn Debug without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/search operation that retrieves UI element information from a React Native debug session. It has no side effects on application state, data, or functionality—it only provides visibility into what elements exist on screen. The severity is low because misuse would only expose debug UI information, not compromise data or trigger unintended actions.
From the tool's definition Tool name and description indicate data retrieval only: 'Find visible elements matching a React Native testID' and 'call get_screen_context + get_test_id_remediation_plan' are query operations. No modifications, deletions, or side effects are mentioned.
Attacks that exploit this kind of access
Find visible elements matching a React Native testID. Use exact first, then contains. If none, call get_screen_context + get_test_id_remediation_plan. It is categorised as a Read tool in the Rn Debug MCP Server, which means it retrieves data without modifying state.
Register the Rn Debug MCP server in PolicyLayer and add a rule for get_elements_by_test_id: 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 Rn Debug. Nothing to install.
get_elements_by_test_id 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_elements_by_test_id 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_elements_by_test_id. 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_elements_by_test_id is provided by the Rn Debug MCP server (rn-debug-mcp). 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 →