Get the state of all devices in the smart home.
AI agents call get_all_states to retrieve information from Smart Home Control MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current state information about smart home devices without creating, modifying, deleting, or executing any actions. It has no side effects and aligns clearly with the 'Read' category (retrieves or queries data). The blast radius of misuse is minimal—an agent could at most learn device states but cannot control or harm devices.
From the tool's definition Tool name 'get_all_states' and description 'Get the state of all devices in the smart home' indicate a pure query/retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Get the state of all devices in the smart home. It is categorised as a Read tool in the Smart Home Control MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smart Home Control MCP Server MCP server in PolicyLayer and add a rule for get_all_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 Smart Home Control MCP Server. Nothing to install.
get_all_states 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 get_all_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.
Set action: deny in the PolicyLayer policy for get_all_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.
get_all_states is provided by the Smart Home Control MCP Server MCP server (surya443/smart-home-mcp-server). 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 →