reboot_device
Reboot an AP, CX switch, AOS-S switch, or gateway. device_type auto-detected if omitted.
This record as markdown: /tools/secure-ssid-centralmcp/reboot-device.md
What reboot_device does on API-Central
AI agents invoke reboot_device 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 reboot_device is rated High
Rebooting a network device is an Execute-class operation that triggers an external action causing temporary service disruption. It is not irreversible data deletion (Destructive), but misuse could knock out network connectivity for many users across switches, APs, or gateways — hence high severity. The tool executes an operational command on live infrastructure.
From the tool's definition Reboot an AP, CX switch, AOS-S switch, or gateway
Attacks that exploit this kind of access
The rule that runs reboot_device 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 reboot_device, this is the rule to start with:
reboot_device 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 reboot_device call is checked against it from then on.
Questions about reboot_device
Reboot an AP, CX switch, AOS-S switch, or gateway. device_type auto-detected 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.
Register the API-Central MCP server in PolicyLayer and add a rule for reboot_device: 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.
reboot_device 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 reboot_device 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 reboot_device. 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.
reboot_device 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