Reboot the router. WARNING: This will disconnect all clients.
AI agents invoke reboot_router to trigger actions in ASUS Merlin Router MCP Server. 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.
Rebooting the router triggers an external system operation that disconnects all connected clients and restarts all services. While not permanently destructive (no data is deleted), it causes significant disruption and is an irreversible trigger action — it cannot be 'undone' once initiated. It falls under Execute as it runs an operation on external infrastructure.
From the tool's definition 'Reboot the router. WARNING: This will disconnect all clients.'
Documented attack patterns abuse exactly the kind of access reboot_router gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ASUS Merlin Router MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reboot_router:
{
"version": "1",
"default": "deny",
"tools": {
"reboot_router": {
"limits": [
{
"counter": "reboot_router_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}reboot_router 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.
Free to start. No card required.
Reboot the router. WARNING: This will disconnect all clients. It is categorised as a Execute tool in the ASUS Merlin Router MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ASUS Merlin Router MCP Server MCP server in PolicyLayer and add a rule for reboot_router: 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 ASUS Merlin Router MCP Server. Nothing to install.
reboot_router 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_router 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_router. 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_router is provided by the ASUS Merlin Router MCP Server MCP server (kcsoukup/asus-merlin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ASUS Merlin Router MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 ASUS Merlin Router MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.