update_label

Update an existing label via WS config/label_registry/update.

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/update-label.md

WHAT IT DOES

What update_label does on Ha Nexus Agent

AI agents use update_label 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 update_label is rated Medium

Updating a label modifies stored configuration data but is reversible (the label can be updated again or reverted). This is a Write operation rather than Read (no retrieval only), Execute (no arbitrary code execution), Destructive (fully reversible), or Financial (no money involved).

From the tool's definition Tool description states 'Update an existing label' — a reversible modification operation via the config/label_registry/update endpoint.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_label Rate-limited

update_label 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": {
    "update_label": {
      "limits": [
        {
          "counter": "update_label_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 update_label call is checked against it from then on.

FAQ

Questions about update_label

What does the update_label tool do? +

Update an existing label via WS config/label_registry/update. 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 update_label? +

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

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

Can I rate-limit update_label? +

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

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

update_label 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

aroflo_create_or_update_record on AroFlo MCP →create-label on Meme MCP Server →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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