reboot_nas · Synology MCP Server MCP: Risk & Policy

WHAT IT DOES

What reboot_nas does on Synology MCP Server

AI agents invoke reboot_nas to trigger actions in Synology 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.

WHY IT NEEDS A POLICY

Why reboot_nas needs a policy

Rebooting the NAS is an external system-level operation that interrupts all running services, active connections, and ongoing tasks (e.g., downloads, shares, backups). While not strictly destructive (data is not deleted), it is a high-impact Execute action — it runs a system command with broad operational consequences.

From the tool's definition 'Reboot the NAS' — triggers a full system reboot of the NAS device; tagged [control][power] and requires explicit power control enablement

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reboot_nas Rate-limited

reboot_nas 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": {
    "reboot_nas": {
      "limits": [
        {
          "counter": "reboot_nas_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 Synology MCP Server, so you can run agents against it safely.

FAQ

Questions about reboot_nas

What does the reboot_nas tool do? +

Reboot the NAS. [control][power] Requires SYNOLOGY_ENABLE_POWER_CONTROL=true. It is categorised as a Execute tool in the Synology MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reboot_nas? +

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

What risk level is reboot_nas? +

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

Can I rate-limit reboot_nas? +

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

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

reboot_nas is provided by the Synology MCP Server MCP server (rafalr100/synology-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.