search_states

Search entities by entity_id, state, friendly_name, device_class, or unit.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/search-states.md

WHAT IT DOES

What search_states does on Mcp Control Plane

AI agents call search_states to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search_states is rated Low

This tool retrieves or queries state information about entities based on various filters. It performs no side effects, creates no data, executes no code, and makes no modifications. It is a straightforward read operation typical of a state management or observability system, consistent with the control plane's Home Assistant and observability components.

From the tool's definition Tool name 'search_states' and description 'Search entities by entity_id, state, friendly_name, device_class, or unit' indicate a query/search operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_states safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_states, this is the rule to start with:

search_states Allowed

search_states is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_states": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every search_states call is checked against it from then on.

FAQ

Questions about search_states

What does the search_states tool do? +

Search entities by entity_id, state, friendly_name, device_class, or unit. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_states? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for search_states: 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 Mcp Control Plane. Nothing to install.

What risk level is search_states? +

search_states is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_states? +

Yes. Add a rate_limit block to the search_states 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 search_states completely? +

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

search_states is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →