Resolve a bundle line/column (e.g. from a CPU profile or stack trace showing index.bundle:69306) back to the original source file and line. Requires Metro to be running.
AI agents call resolve_source_location to retrieve information from Mcp Rn Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only source map lookup, translating minified bundle coordinates to original source locations. It retrieves/queries information without modifying any data or triggering side effects.
From the tool's definition Resolve a bundle line/column... back to the original source file and line. Requires Metro to be running.
Attacks that exploit this kind of access
Resolve a bundle line/column (e.g. from a CPU profile or stack trace showing index.bundle:69306) back to the original source file and line. Requires Metro to be running. It is categorised as a Read tool in the Mcp Rn Devtools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Rn Devtools MCP server in PolicyLayer and add a rule for resolve_source_location: 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 Mcp Rn Devtools. Nothing to install.
resolve_source_location 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 resolve_source_location 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 resolve_source_location. 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.
resolve_source_location is provided by the Mcp Rn Devtools MCP server (pablonortiz/mcp-rn-devtools). 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 →