save_energy_prefs
Save Energy Dashboard preferences (WS energy/save_prefs); only the fields you pass are sent.
This record as markdown: /tools/fistacho-ha-nexus-agent/save-energy-prefs.md
What save_energy_prefs does on Ha Nexus Agent
AI agents use save_energy_prefs to create or update resources in Ha Nexus Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ha Nexus Agent environment.
Why save_energy_prefs is rated Medium
This tool modifies user configuration/preferences data for the Energy Dashboard in Home Assistant. It is reversible (preferences can be changed again), making it a Write operation rather than Destructive. Severity is medium because incorrect energy preference changes could affect energy monitoring, reporting, or automation logic, but would not directly control critical home systems or cause data loss.
From the tool's definition Tool name 'save_energy_prefs' and description 'Save Energy Dashboard preferences' indicates creation or modification of user preference data. The mechanism uses WebSocket endpoint `energy/save_prefs` which persists preference state.
Attacks that exploit this kind of access
The rule that runs save_energy_prefs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_energy_prefs, this is the rule to start with:
save_energy_prefs stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every save_energy_prefs call is checked against it from then on.
Questions about save_energy_prefs
Save Energy Dashboard preferences (WS energy/save_prefs); only the fields you pass are sent. It is categorised as a Write tool in the Ha Nexus Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for save_energy_prefs: 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 Ha Nexus Agent. Nothing to install.
save_energy_prefs 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 save_energy_prefs 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 save_energy_prefs. 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.
save_energy_prefs is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ha Nexus Agent, and thousands of servers like it.
This server
Across the catalogue