set_entity_exposure

Expose or hide an entity to a voice assistant.

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-entity-exposure.md

WHAT IT DOES

What set_entity_exposure does on Ha Nexus Agent

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

This tool modifies the exposure state of a smart home entity to voice assistants, which is a reversible configuration change (entities can be re-exposed or hidden). It does not destroy data, execute arbitrary commands, or cause financial impact.

From the tool's definition Tool name 'set_entity_exposure' and description 'Expose or hide an entity to a voice assistant' indicate modification of entity configuration settings.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_entity_exposure Rate-limited

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

FAQ

Questions about set_entity_exposure

What does the set_entity_exposure tool do? +

Expose or hide an entity to a voice assistant. 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_entity_exposure? +

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

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

Can I rate-limit set_entity_exposure? +

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

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

set_entity_exposure 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 →