set_input_select
Set an input_select to a specific option.
This record as markdown: /tools/fistacho-ha-nexus-agent/set-input-select.md
What set_input_select does on Ha Nexus Agent
AI agents use set_input_select 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.
Why set_input_select is rated Medium
This tool modifies state in a Home Assistant smart home system by changing an input_select entity to a specified option. This is a reversible write operation (the value can be changed back), not destructive.
From the tool's definition Tool name 'set_input_select' and description 'Set an input_select to a specific option' indicates modification of Home Assistant input_select entity state to a new value.
Attacks that exploit this kind of access
The rule that runs set_input_select 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_input_select, this is the rule to start with:
set_input_select 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every set_input_select call is checked against it from then on.
Questions about set_input_select
Set an input_select to a specific option. 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.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for set_input_select: 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.
set_input_select is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_input_select 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.
Set action: deny in the PolicyLayer policy for set_input_select. 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.
set_input_select 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.
This server
Across the catalogue