port_bounce · API-Central MCP: Risk & Policy

WHAT IT DOES

What port_bounce does on API-Central

AI agents invoke port_bounce 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 port_bounce needs a policy

Bouncing a port forces a link reset on network infrastructure, temporarily taking down connected devices/sessions. This is an external operation with real network impact (service disruption) but is generally recoverable, placing it in Execute rather than Destructive. However, misuse could affect many downstream users if applied to uplinks or critical ports, warranting high severity.

From the tool's definition 'Link-reset (bounce) switch/gateway ports' — triggers an external network operation that disrupts active port connectivity

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

port_bounce Rate-limited

port_bounce 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": {
    "port_bounce": {
      "limits": [
        {
          "counter": "port_bounce_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 port_bounce

What does the port_bounce tool do? +

Link-reset (bounce) switch/gateway ports (async, polls ~60s). 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 port_bounce? +

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

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

Can I rate-limit port_bounce? +

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

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

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