add_grid_return

Add a grid return flow (flow_to, e.g. solar export) to the Energy Dashboard's grid source.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/add-grid-return.md

WHAT IT DOES

What add_grid_return does on Ha Nexus Agent

AI agents use add_grid_return 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.

RISK

Why add_grid_return is rated Medium

This tool creates or modifies dashboard/energy configuration data in a reversible manner (the grid return flow can be removed or modified). It does not execute arbitrary commands, delete data irreversibly, or move money.

From the tool's definition Tool name and description indicate 'Add a grid return flow' which modifies the Energy Dashboard configuration by adding grid return data. The description explicitly states it adds to 'grid source' configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_grid_return Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_grid_return": {
      "limits": [
        {
          "counter": "add_grid_return_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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 add_grid_return call is checked against it from then on.

FAQ

Questions about add_grid_return

What does the add_grid_return tool do? +

Add a grid return flow (flow_to, e.g. solar export) to the Energy Dashboard's grid source. 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.

How do I enforce a policy on add_grid_return? +

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

add_grid_return is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_grid_return? +

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

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

add_grid_return 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

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →