Manage HomeKit automations. List existing automations, inspect their events and linked scenes, create automations triggered by any characteristic change (button presses, motion sensors, contact sensors, occupancy, etc.) or by a time of day (clock or sunrise/sunset), delete automations, or enable/...
AI agents invoke homekit_automations to trigger actions in HomeClaw. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool can create, delete, enable, and disable HomeKit automations that trigger real-world actions (lights, locks, scenes, etc.). Creating or modifying automations causes external operations to execute automatically in the physical environment. Deletion is irreversible but the primary function is automation management/execution.
From the tool's definition create automations triggered by any characteristic change...or by a time of day...delete automations, or enable/disable them
Documented attack patterns abuse exactly the kind of access homekit_automations 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_automations:
{
"version": "1",
"default": "deny",
"tools": {
"homekit_automations": {
"limits": [
{
"counter": "homekit_automations_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}homekit_automations stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage HomeKit automations. List existing automations, inspect their events and linked scenes, create automations triggered by any characteristic change (button presses, motion sensors, contact sensors, occupancy, etc.) or by a time of day (clock or sunrise/sunset), delete automations, or enable/disable them. For characteristic-change triggers use action=create with press_type (buttons) or characteristic+trigger_value (sensors). For time-of-day triggers use action=create_time with the. It is categorised as a Execute tool in the HomeClaw MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the HomeClaw MCP server in PolicyLayer and add a rule for homekit_automations: 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_automations is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the homekit_automations 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_automations. 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_automations 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.