Clear any active element highlight
AI agents call clear_highlight to permanently remove resources in React Devtools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call clear_highlight doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from React Devtools is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Clear any active element highlight. It is categorised as a Destructive tool in the React Devtools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the React Devtools MCP server in PolicyLayer and add a rule for clear_highlight: 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.
clear_highlight is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_highlight 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 clear_highlight. 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.
clear_highlight 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 →