Set home/away status
AI agents use set_home_status to create or update resources in HC3 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HC3 MCP Server environment.
The tool creates or modifies data reversibly by changing the home/away status flag in the smart home system. This is not a Read operation (it doesn't just query status), not Destructive (the change is reversible), not Execute (it doesn't run arbitrary code or commands), and not Financial.
From the tool's definition Tool description states 'Set home/away status' which modifies the home automation system's status state. This is a reversible configuration change that alters system state (from away to home or vice versa), similar to other Write category operations like…
Attacks that exploit this kind of access
Set home/away status. It is categorised as a Write tool in the HC3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for set_home_status: 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 HC3 MCP Server. Nothing to install.
set_home_status 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 set_home_status 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 set_home_status. 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.
set_home_status is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →