Get details for a single schedule rule by id.
AI agents call get_schedule_rule 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 queries and retrieves schedule rule information from the smart home system. It has no capability to modify, delete, or execute actions. The user is simply fetching existing configuration data by ID. This is consistent with other read operations on the server (get_device_status, get_current_schedule, get_events, etc.).
From the tool's definition Tool name 'get_schedule_rule' and description 'Get details for a single schedule rule by id' indicate a retrieval operation with no modifications or side effects. The verb 'Get' and the lack of any state-changing language confirm read-only behavior.
Attacks that exploit this kind of access
Get details for a single schedule rule by id. 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_schedule_rule: 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_schedule_rule 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_schedule_rule 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_schedule_rule. 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_schedule_rule 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 →