run_cloud_sync · Truenas Ws MCP: Risk & Policy

WHAT IT DOES

What run_cloud_sync does on Truenas Ws

AI agents invoke run_cloud_sync to trigger actions in Truenas Ws. 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_cloud_sync needs a policy

Although cloud sync does not inherently destroy data or move money, it executes an operation that transfers data to external cloud storage. The blast radius is high because a misconfigured or unintended sync could expose sensitive data to unauthorized cloud accounts, corrupt synchronization state, or trigger unexpected data transfers.

From the tool's definition Tool performs 'Trigger a cloud sync task to run immediately' — an external operation whose effects (data synchronization to cloud storage) depend on the configured task and cannot be easily reversed or undone if misconfigured.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_cloud_sync Rate-limited

run_cloud_sync 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_cloud_sync": {
      "limits": [
        {
          "counter": "run_cloud_sync_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 Truenas Ws, so you can run agents against it safely.

FAQ

Questions about run_cloud_sync

What does the run_cloud_sync tool do? +

Trigger a cloud sync task to run immediately. It is categorised as a Execute tool in the Truenas Ws 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_cloud_sync? +

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

What risk level is run_cloud_sync? +

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

Can I rate-limit run_cloud_sync? +

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

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

run_cloud_sync is provided by the Truenas Ws MCP server (thoriphes/truenas-ws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.