Get the controller event log between two timestamps (Unix epoch ms). Default range is the last 7 days.
AI agents call get_events to retrieve information from Home Controller without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns event log data without modifying, deleting, or executing any actions. It is a passive query operation analogous to 'get_activity_log' and other Read-category tools on the same server. The worst-case misuse would be unauthorized information disclosure about home automation activity, which poses low risk compared to tools that modify device state or perform destructive operations.
From the tool's definition Tool name 'get_events' and description 'Get the controller event log between two timestamps' indicates a retrieval operation with no side effects. It queries historical event data within a specified time range.
Attacks that exploit this kind of access
Get the controller event log between two timestamps (Unix epoch ms). Default range is the last 7 days. It is categorised as a Read tool in the Home Controller MCP Server, which means it retrieves data without modifying state.
Register the Home Controller MCP server in PolicyLayer and add a rule for get_events: 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 Home Controller. Nothing to install.
get_events 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 get_events 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 get_events. 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.
get_events is provided by the Home Controller MCP server (winsthuang/home-controller). 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 →