set_component_filters · React Devtools MCP: Risk & Policy

WHAT IT DOES

What set_component_filters does on React Devtools

AI agents use set_component_filters 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.

WHY IT NEEDS A POLICY

Why set_component_filters needs a policy

This tool modifies filter settings to hide components in a React debugging view, which is a write operation that changes the UI state of the DevTools display. The change is reversible (filters can be adjusted again), so it does not qualify as destructive. It has low severity because it only affects the visibility settings in a development debugging interface with no impact on actual application data or functionality.

From the tool's definition Tool name 'set_component_filters' with description 'Set component filters (hide certain components)' indicates modification of display/filter settings. The verb 'set' and action of hiding components represents a state change that is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_component_filters Rate-limited

set_component_filters stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_component_filters": {
      "limits": [
        {
          "counter": "set_component_filters_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches React Devtools, so you can run agents against it safely.

FAQ

Questions about set_component_filters

What does the set_component_filters tool do? +

Set component filters (hide certain components). 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.

How do I enforce a policy on set_component_filters? +

Register the React Devtools MCP server in PolicyLayer and add a rule for set_component_filters: 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.

What risk level is set_component_filters? +

set_component_filters is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_component_filters? +

Yes. Add a rate_limit block to the set_component_filters 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.

How do I block set_component_filters completely? +

Set action: deny in the PolicyLayer policy for set_component_filters. 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.

What MCP server provides set_component_filters? +

set_component_filters 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.