Get source file location (file, line, column) for a component. Use selector or uid from take_snapshot.
AI agents call get_component_source 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.
This tool performs a pure read/query operation returning source code location information. It has no side effects, does not modify state, execute code, or trigger external operations. The severity is low because the information returned (file locations and line numbers) is non-sensitive metadata that does not expose data access or control risks.
From the tool's definition Tool description states it 'Get[s] source file location' with no modification or execution capability. It retrieves metadata about component location (file, line, column) based on a selector or uid parameter.
Attacks that exploit this kind of access
Get source file location (file, line, column) for a component. Use selector or uid from take_snapshot. 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 get_component_source: 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.
get_component_source 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_component_source 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_component_source. 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_component_source 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 →