remove_energy_source

Remove an energy source identified by its stat_energy_from (also strips matching grid flow_from entries).

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/remove-energy-source.md

What remove_energy_source does on Ha Nexus Agent

AI agents call remove_energy_source to permanently remove resources in Ha Nexus Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_energy_source is rated Critical

This tool permanently deletes energy source configuration and related grid flow entries from a Home Assistant energy management system. The operation cannot be undone without manual reconfiguration, making it destructive rather than merely a write operation. In a smart home context, removing energy sources affects billing calculations, monitoring, and automation logic.

From the tool's definition remove_energy_source: 'Remove an energy source' and 'strips matching grid flow_from entries' — uses destructive verb 'remove' and 'strips', indicating irreversible deletion of configuration data

Questions about remove_energy_source

What does the remove_energy_source tool do? +

Remove an energy source identified by its stat_energy_from (also strips matching grid flow_from entries). It is categorised as a Destructive tool in the Ha Nexus Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_energy_source? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for remove_energy_source: 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 remove_energy_source? +

remove_energy_source is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_energy_source? +

Yes. Add a rate_limit block to the remove_energy_source 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 remove_energy_source completely? +

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.