Build deterministic patch/remediation guidance when a desired testID is missing. Recommended flow: get_screen_test_ids -> get_elements_by_test_id (exact/contains) -> this tool -> reload_app -> retry lookup.
AI agents call get_test_id_remediation_plan 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 tool generates remediation guidance and analysis based on missing test IDs—a read-only diagnostic operation. It retrieves information and provides recommendations but does not execute code, modify state, delete data, or commit financial actions. The guidance it produces is informational in nature, meant to assist developers in understanding how to fix missing test IDs.
From the tool's definition Tool description states it 'Build[s] deterministic patch/remediation guidance' for missing testIDs. The recommended flow shows it as an informational step between lookups (get_screen_test_ids -> get_elements_by_test_id -> this tool -> reload_app), indicating…
Attacks that exploit this kind of access
Build deterministic patch/remediation guidance when a desired testID is missing. Recommended flow: get_screen_test_ids -> get_elements_by_test_id (exact/contains) -> this tool -> reload_app -> retry lookup. 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_test_id_remediation_plan: 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_test_id_remediation_plan 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_test_id_remediation_plan 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_test_id_remediation_plan. 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_test_id_remediation_plan 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 →