Check HomeClaw status — shows connectivity, home count, and accessory count.
AI agents call homekit_status to retrieve information from HomeClaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries the current status of the HomeClaw system. It returns informational data (connectivity status, counts) with no side effects, no code execution, and no data modification. This is a classic Read category tool. Severity is low because status checks pose minimal risk even if misused by an AI agent — they cannot control devices, modify configurations, or cause harm.
From the tool's definition Tool name 'homekit_status' and description 'Check HomeClaw status — shows connectivity, home count, and accessory count' indicate a query operation that retrieves status information without modifying or executing actions.
Documented attack patterns abuse exactly the kind of access homekit_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HomeClaw, and nothing reaches the server without passing your rules. This is the rule we recommend for homekit_status:
{
"version": "1",
"default": "deny",
"tools": {
"homekit_status": {}
}
}homekit_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check HomeClaw status — shows connectivity, home count, and accessory count. It is categorised as a Read tool in the HomeClaw MCP Server, which means it retrieves data without modifying state.
Register the HomeClaw MCP server in PolicyLayer and add a rule for homekit_status: 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 HomeClaw. Nothing to install.
homekit_status 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 homekit_status 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 homekit_status. 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.
homekit_status is provided by the HomeClaw MCP server (omarshahine/homeclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 HomeClaw tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 HomeClaw tools catalogued and risk-classified — across an index of 42,500+ MCP servers.