Get the current state of the Home Assistant core
AI agents call tools-system-core-state to retrieve information from Home Assistant MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves the current state of the Home Assistant core system. It performs no data modification, deletion, or external actions—it only fetches and returns existing state information. This is a classic Read category operation. Severity is low because retrieving system state information poses minimal risk even if misused; it exposes no sensitive credentials or destructive capabilities.
From the tool's definition Tool name 'tools-system-core-state' and description 'Get the current state' indicate a read-only query operation that retrieves status information without modification.
Attacks that exploit this kind of access
Get the current state of the Home Assistant core. It is categorised as a Read tool in the Home Assistant MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Home Assistant MCP Server MCP server in PolicyLayer and add a rule for tools-system-core-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 Home Assistant MCP Server. Nothing to install.
tools-system-core-state 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 tools-system-core-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 tools-system-core-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.
tools-system-core-state is provided by the Home Assistant MCP Server MCP server (oleander/home-assistant-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 →