Manage webhook configuration for pushing HomeKit events to OpenClaw or other services. Actions: setup (configure URL, token, and enable in one step), test (send a test event and show the HTTP response), reset (reset the circuit breaker), status (show webhook health and delivery stats).
AI agents call homekit_webhook to permanently remove resources in HomeClaw — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call homekit_webhook doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from HomeClaw is gone — there is no undo for destructive operations.
Documented attack patterns abuse exactly the kind of access homekit_webhook 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_webhook:
{
"version": "1",
"default": "deny",
"hide": [
"homekit_webhook"
]
}homekit_webhook disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Manage webhook configuration for pushing HomeKit events to OpenClaw or other services. Actions: setup (configure URL, token, and enable in one step), test (send a test event and show the HTTP response), reset (reset the circuit breaker), status (show webhook health and delivery stats). It is categorised as a Destructive tool in the HomeClaw MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HomeClaw MCP server in PolicyLayer and add a rule for homekit_webhook: 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_webhook is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the homekit_webhook 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_webhook. 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_webhook 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.