poe_bounce
Power-cycle PoE on switch/gateway ports (async, polls ~60s).
This record as markdown: /tools/secure-ssid-centralmcp/poe-bounce.md
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 poe_bounce is rated High
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
The rule that runs poe_bounce 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 poe_bounce, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every poe_bounce call is checked against it from then on.
Questions about poe_bounce
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.
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.
poe_bounce is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on API-Central, and thousands of servers like it.
Across the catalogue