Search for components by name
AI agents call search_components 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 searches for and retrieves component metadata (names, locations) from a React application's component tree. It has no side effects, does not execute code, does not modify state, and does not delete anything. It is a read-only query operation with minimal blast radius—the worst case is returning incorrect or exhaustive search results, which poses no security risk beyond information disclosure.
From the tool's definition Tool name 'search_components' and description 'Search for components by name' indicate a query operation that retrieves information about React components without modifying or executing anything. The action is purely informational.
Attacks that exploit this kind of access
Search for components by name. 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 search_components: 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.
search_components 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 search_components 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 search_components. 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.
search_components 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 →