poe_bounce · API-Central MCP: Risk & Policy

WHAT IT DOES

What poe_bounce does on API-Central

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

This tool executes a physical operation (power-cycling PoE ports) on network infrastructure. It triggers an external operation that disrupts power to connected devices (phones, cameras, APs, IoT devices). While PoE ports come back online after the cycle (making it not strictly destructive/irreversible), misuse can cause significant service disruption across potentially many connected devices.

From the tool's definition Power-cycle PoE on switch/gateway ports

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

poe_bounce Rate-limited

poe_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": {
    "poe_bounce": {
      "limits": [
        {
          "counter": "poe_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 poe_bounce

What does the poe_bounce tool do? +

Power-cycle PoE on 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 poe_bounce? +

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

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

Can I rate-limit poe_bounce? +

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

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

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

// THE FULL RECORD

poe_bounce is one line of API-Central's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →