Get recent HomeKit events — characteristic changes, scene triggers, and accessory control actions. Use to understand what happened recently in the home.
AI agents call homekit_events 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 retrieves and queries historical event data from HomeKit without creating, modifying, deleting, or executing any changes to the smart home system. It is purely informational, similar to viewing logs or status. The minimal blast radius is limited to information disclosure about past events, which is the lowest severity impact.
From the tool's definition Tool description states 'Get recent HomeKit events' and 'use to understand what happened recently in the home.' The verb 'Get' and the read-only purpose of retrieving historical event logs indicate no modification or side effects.
Documented attack patterns abuse exactly the kind of access homekit_events 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_events:
{
"version": "1",
"default": "deny",
"tools": {
"homekit_events": {}
}
}homekit_events 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.
Get recent HomeKit events — characteristic changes, scene triggers, and accessory control actions. Use to understand what happened recently in the home. 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_events: 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_events 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_events 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_events. 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_events 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.