Get water consumption data for a device. Duration format: YYYY/MM/DD for daily, YYYY/MM for monthly, YYYY for yearly
AI agents call get_consumption 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 historical water consumption metrics from monitoring devices and returns read-only data. It has no side effects, does not modify state, and poses minimal risk even if misused by an AI agent—the worst outcome would be retrieving consumption data the user did not intend to expose, which is a privacy concern rather than a safety/destructive risk. Classified as Read with low severity.
From the tool's definition Tool name "get_consumption" and description indicate retrieval of water consumption data with no modification capabilities. The duration parameters (YYYY/MM/DD, YYYY/MM, YYYY) are query filters, not write operations.
Attacks that exploit this kind of access
Get water consumption data for a device. Duration format: YYYY/MM/DD for daily, YYYY/MM for monthly, YYYY for yearly. 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_consumption: 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_consumption 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_consumption 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_consumption. 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_consumption 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 →