gateway_halt

Halt an Aruba gateway (POST .../halt). Requires elicited confirmation — this stops

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/gateway-halt.md

WHAT IT DOES

What gateway_halt does on API-Central

AI agents call gateway_halt to permanently remove resources in API-Central, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why gateway_halt is rated Critical

Halting a gateway stops its operation, cutting off network services for potentially large numbers of users. While a gateway can theoretically be restarted, the act of halting is a disruptive, non-reversible-in-state action (the running state is destroyed). The description explicitly mentions 'elicited confirmation' indicating the severity.

From the tool's definition 'Halt an Aruba gateway' and 'this stops' — halting a network gateway is an irreversible operational action that immediately disrupts network connectivity for all users/devices depending on that gateway.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gateway_halt safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gateway_halt, this is the rule to start with:

gateway_halt Hidden

gateway_halt is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gateway_halt"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every gateway_halt call is checked against it from then on.

FAQ

Questions about gateway_halt

What does the gateway_halt tool do? +

Halt an Aruba gateway (POST .../halt). Requires elicited confirmation — this stops. It is categorised as a Destructive tool in the API-Central MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gateway_halt? +

Register the API-Central MCP server in PolicyLayer and add a rule for gateway_halt: 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 API-Central. Nothing to install.

What risk level is gateway_halt? +

gateway_halt is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gateway_halt? +

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

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

gateway_halt is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →