press_button

Press a button entity.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

High RISK CLASS

Category Execute

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/press-button.md

WHAT IT DOES

What press_button does on Ha Nexus Agent

AI agents invoke press_button to trigger actions in Ha Nexus Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why press_button is rated High

Pressing a button entity triggers an action in the real world or smart home system. The effect depends on what the button is configured to do (could range from innocuous to significant), making it an Execute-category tool. Severity is medium because button presses can trigger automations, scenes, or physical device actions with potentially wide blast radius depending on configuration.

From the tool's definition Press a button entity — triggers an external operation (activating a physical or virtual button in the smart home)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

press_button Rate-limited

press_button stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "press_button": {
      "limits": [
        {
          "counter": "press_button_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 press_button call is checked against it from then on.

FAQ

Questions about press_button

What does the press_button tool do? +

Press a button entity. It is categorised as a Execute tool in the Ha Nexus Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on press_button? +

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

press_button is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit press_button? +

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

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

press_button 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 → High-risk tools on this server →

Across the catalogue

qt_key_press on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →