Get source location for an element
AI agents call get_element_source to retrieve information from React Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves information about source code locations for React components. It has no side effects, does not modify data, execute code, or perform destructive operations. It is a pure read operation providing debugging visibility into a React application's component structure and source mapping.
From the tool's definition Tool name is 'get_element_source' and description states it 'Get source location for an element'. This retrieves metadata about where a component is defined in the codebase, with no modification or execution capabilities.
Attacks that exploit this kind of access
Get source location for an element. It is categorised as a Read tool in the React Devtools MCP Server, which means it retrieves data without modifying state.
Register the React Devtools MCP server in PolicyLayer and add a rule for get_element_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 Devtools. Nothing to install.
get_element_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_element_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_element_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_element_source is provided by the React Devtools MCP server (skylarbarrera/react-devtools-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 →