list_button_toggle_features

A read tool on the Ha Nexus Agent MCP server.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/list-button-toggle-features.md

WHAT IT DOES

What list_button_toggle_features does on Ha Nexus Agent

AI agents call list_button_toggle_features to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_button_toggle_features is rated Low

Despite the empty description providing no explicit confirmation, the tool name 'list_button_toggle_features' strongly suggests it retrieves or enumerates button-toggle features from the Home Assistant smart home system. This is characteristic of Read operations. The tool does not create, modify, delete, or execute actions—it appears to query feature availability.

From the tool's definition Tool name contains 'list' which is a retrieval operation; the verb 'list' is typically associated with querying or enumerating data without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_button_toggle_features Allowed

list_button_toggle_features is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_button_toggle_features": {}
  }
}

ALLOW ONLY 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 list_button_toggle_features call is checked against it from then on.

FAQ

Questions about list_button_toggle_features

What does the list_button_toggle_features tool do? +

list_button_toggle_features is a read tool on the Ha Nexus Agent MCP server. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_button_toggle_features? +

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

list_button_toggle_features is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_button_toggle_features? +

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

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

list_button_toggle_features 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →