Get the chain of components that rendered this element
AI agents call get_owners_list 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 retrieves debugging information about React component ancestry/chain—a read-only inspection operation. It has no side effects, does not execute code, and does not modify any application state. The blast radius of misuse is minimal, as an agent could only gain visibility into component structure, which is already visible through normal React DevTools inspection.
From the tool's definition Tool name 'get_owners_list' and description 'Get the chain of components that rendered this element' indicate a query operation that retrieves component hierarchy information without modifying state.
Attacks that exploit this kind of access
Get the chain of components that rendered this 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_owners_list: 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_owners_list 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_owners_list 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_owners_list. 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_owners_list 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 →