disconnect_client · API-Central MCP: Risk & Policy

WHAT IT DOES

What disconnect_client does on API-Central

AI agents invoke disconnect_client to trigger actions in API-Central. 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.

WHY IT NEEDS A POLICY

Why disconnect_client needs a policy

This tool triggers an external network operation (deauthentication/disassociation of a wireless client) that has immediate real-world effects. It is not a simple data write — it forces termination of a live network session. While the client can reconnect, the act itself is an external operation with disruptive impact. Misuse could deny network access to legitimate users at scale, hence high severity.

From the tool's definition 'Force-disconnect a wireless client by MAC address' — actively terminates an existing wireless client session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_client Rate-limited

disconnect_client 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": {
    "disconnect_client": {
      "limits": [
        {
          "counter": "disconnect_client_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches API-Central, so you can run agents against it safely.

FAQ

Questions about disconnect_client

What does the disconnect_client tool do? +

Force-disconnect a wireless client by MAC address. ap_serial auto-looked up if omitted. It is categorised as a Execute tool in the API-Central MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on disconnect_client? +

Register the API-Central MCP server in PolicyLayer and add a rule for disconnect_client: 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 disconnect_client? +

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

Can I rate-limit disconnect_client? +

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

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

disconnect_client 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.