Override a state value on a class component
AI agents use override_state to create or update resources in React Devtools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your React Devtools environment.
This tool modifies the runtime state of a React class component, which is a write operation that changes application data/behavior. It could cause significant issues if misused—altering component state can break UI logic, trigger unintended side effects, or corrupt application state. While potentially reversible by re-rendering or resetting, it directly mutates live application state, making it high severity.
From the tool's definition Override a state value on a class component
Attacks that exploit this kind of access
Override a state value on a class component. It is categorised as a Write tool in the React Devtools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the React Devtools MCP server in PolicyLayer and add a rule for override_state: 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.
override_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the override_state 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 override_state. 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.
override_state 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 →