Manage HomeKit structure: rename accessories, assign rooms (with UUID support for duplicate names), create/rename/remove rooms, remove accessories, create/remove zones, and manage zone membership. All actions support dry_run for safe previews.
AI agents use homekit_manage to create or update resources in HomeClaw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HomeClaw environment.
An AI agent can call homekit_manage faster than any human can review — one bad instruction and it creates or modifies resources in HomeClaw by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access homekit_manage 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_manage:
{
"version": "1",
"default": "deny",
"tools": {
"homekit_manage": {
"limits": [
{
"counter": "homekit_manage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}homekit_manage stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage HomeKit structure: rename accessories, assign rooms (with UUID support for duplicate names), create/rename/remove rooms, remove accessories, create/remove zones, and manage zone membership. All actions support dry_run for safe previews. It is categorised as a Write tool in the HomeClaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HomeClaw MCP server in PolicyLayer and add a rule for homekit_manage: 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_manage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the homekit_manage 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_manage. 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_manage 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.