run_backup_task · Synology MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_backup_task does on Synology MCP Server

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

While backups are generally protective operations, this tool executes a task whose side effects (resource consumption, storage I/O, network bandwidth) cannot be precisely predicted without knowing the backup target, scope, and current system state. It is not a simple read (no data retrieval), write (no data creation/modification by the user), or destructive action.

From the tool's definition Tool name 'run_backup_task' combined with description 'Start a Hyper Backup task immediately' indicates execution of a potentially complex, system-level operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_backup_task Rate-limited

run_backup_task 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": {
    "run_backup_task": {
      "limits": [
        {
          "counter": "run_backup_task_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 run_backup_task

What does the run_backup_task tool do? +

Start a Hyper Backup task immediately. [control]. 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 run_backup_task? +

Register the Synology MCP Server MCP server in PolicyLayer and add a rule for run_backup_task: 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 run_backup_task? +

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

Can I rate-limit run_backup_task? +

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

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

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