Get an LLM-optimized device map organized by home/zone/room with semantic types, auto-generated aliases, controllable characteristics, and state summaries. Use this to understand the full device landscape before controlling devices.
AI agents call homekit_device_map 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 queries and retrieves HomeKit device information organized by structure (home/zone/room). It returns a map/summary of devices and their characteristics but does not create, modify, delete, execute actions, or transfer funds. It is purely informational and used as a reference before other control operations.
From the tool's definition Tool description states 'Get an LLM-optimized device map' and 'understand the full device landscape' — explicitly a retrieval operation with no modification or control capability.
Documented attack patterns abuse exactly the kind of access homekit_device_map 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_device_map:
{
"version": "1",
"default": "deny",
"tools": {
"homekit_device_map": {}
}
}homekit_device_map 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 an LLM-optimized device map organized by home/zone/room with semantic types, auto-generated aliases, controllable characteristics, and state summaries. Use this to understand the full device landscape before controlling devices. 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_device_map: 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_device_map 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_device_map 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_device_map. 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_device_map 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.