get_energy_prefs

Return the full Home Assistant Energy Dashboard preferences (WS energy/get_prefs).

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/get-energy-prefs.md

WHAT IT DOES

What get_energy_prefs does on Ha Nexus Agent

AI agents call get_energy_prefs to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_energy_prefs is rated Low

This tool retrieves configuration data about energy preferences from Home Assistant. It performs a read-only query (WS `energy/get_prefs`) that returns existing state without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could view energy settings but cannot modify them or trigger physical changes to the smart home.

From the tool's definition Tool name is 'get_energy_prefs' and description states 'Return the full Home Assistant Energy Dashboard preferences'. The verb 'return' and 'get' indicate data retrieval with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_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 get_energy_prefs, this is the rule to start with:

get_energy_prefs Allowed

get_energy_prefs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_energy_prefs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every get_energy_prefs call is checked against it from then on.

FAQ

Questions about get_energy_prefs

What does the get_energy_prefs tool do? +

Return the full Home Assistant Energy Dashboard preferences (WS energy/get_prefs). It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_energy_prefs? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_energy_prefs? +

get_energy_prefs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_energy_prefs? +

Yes. Add a rate_limit block to the get_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.

How do I block get_energy_prefs completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_energy_prefs? +

get_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.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →