central_bounce_port · Central MCP: Risk & Policy

WHAT IT DOES

What central_bounce_port does on Central

AI agents invoke central_bounce_port to trigger actions in 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 central_bounce_port needs a policy

'Bouncing' a port is a well-known network operations action that disables and re-enables a switch/AP port, causing connected devices to lose and re-establish connectivity. This is an Execute-category action with high severity because misuse could disrupt network connectivity for clients connected to that port. The description is empty, but the name strongly implies this operation.

From the tool's definition Tool name 'central_bounce_port' — 'bounce' in networking means disabling and re-enabling a port, which triggers an external operation on network infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

central_bounce_port Rate-limited

central_bounce_port 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": {
    "central_bounce_port": {
      "limits": [
        {
          "counter": "central_bounce_port_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 Central, so you can run agents against it safely.

FAQ

Questions about central_bounce_port

What does the central_bounce_port tool do? +

central_bounce_port. It is categorised as a Execute tool in the 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 central_bounce_port? +

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

What risk level is central_bounce_port? +

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

Can I rate-limit central_bounce_port? +

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

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

central_bounce_port is provided by the Central MCP server (karthikskumar98/central-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.