run_scheduled_task · Synology MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_scheduled_task does on Synology MCP Server

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

This tool invokes arbitrary scheduled tasks on a Synology NAS without showing what the task will do. A scheduled task could perform destructive operations (data deletion, system reconfiguration), financial actions (if integrated with external services), or side effects beyond the user's immediate intent. The blast radius is high because the operator may not know the full consequences of triggering an unfamiliar task.

From the tool's definition Tool description explicitly states 'Trigger a scheduled task to run immediately' — this executes a pre-configured task whose effects depend on what that task does (backup, script, system maintenance, etc.).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_scheduled_task Rate-limited

run_scheduled_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_scheduled_task": {
      "limits": [
        {
          "counter": "run_scheduled_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_scheduled_task

What does the run_scheduled_task tool do? +

Trigger a scheduled task to run 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_scheduled_task? +

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

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

Can I rate-limit run_scheduled_task? +

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

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

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