turn_off

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/turn-off.md

WHAT IT DOES

What turn_off does on Ha Nexus Agent

AI agents call turn_off 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 turn_off is rated Low

Even though turn_off only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

turn_off Allowed

turn_off 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": {
    "turn_off": {}
  }
}

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

FAQ

Questions about turn_off

What does the turn_off tool do? +

turn_off 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 turn_off? +

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

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

Can I rate-limit turn_off? +

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

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

turn_off 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 315 Ha Nexus Agent tools →

Across the catalogue

The MCP Attack Database →

Guides

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