set_preferred_pipeline

Set the default Assist pipeline (used when no pipeline is specified).

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/set-preferred-pipeline.md

WHAT IT DOES

What set_preferred_pipeline does on Ha Nexus Agent

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

This tool creates or modifies data reversibly by changing the default Assist pipeline setting. While it affects how voice/automation requests are routed, the change is non-destructive and can be undone by setting a different pipeline. The impact is primarily configuration-level rather than triggering external operations (Execute) or financial/destructive consequences.

From the tool's definition Tool description states 'Set the default Assist pipeline' — this modifies a configuration setting in Home Assistant. The verb 'set' indicates a write operation that changes system state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_preferred_pipeline Rate-limited

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

FAQ

Questions about set_preferred_pipeline

What does the set_preferred_pipeline tool do? +

Set the default Assist pipeline (used when no pipeline is specified). 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 set_preferred_pipeline? +

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

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

Can I rate-limit set_preferred_pipeline? +

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

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

set_preferred_pipeline 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

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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