Medium Risk

cloudsync_create

Create a new cloud sync task

How to control cloudsync_create ↓

What cloudsync_create does on Truenas

AI agents use cloudsync_create to create or update resources in Truenas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas environment.

Medium Risk

Why cloudsync_create needs a policy

This tool creates a new cloud synchronization task, which is a reversible Write operation. While it involves cloud connectivity and data movement, the core action is configuration creation rather than data deletion, code execution, or financial transaction.

From the tool's definition Tool name is 'cloudsync_create' and description states 'Create a new cloud sync task' — the verb 'create' indicates a Write operation that establishes a new reversible configuration.

Documented attack patterns abuse exactly the kind of access cloudsync_create gives an agent:

How to control cloudsync_create

PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for cloudsync_create:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cloudsync_create": {
      "limits": [
        {
          "counter": "cloudsync_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

cloudsync_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Truenas — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cloudsync_create

What does the cloudsync_create tool do? +

Create a new cloud sync task. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cloudsync_create? +

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

What risk level is cloudsync_create? +

cloudsync_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cloudsync_create? +

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

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

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

Enforce policy on every Truenas tool call.

Start from Truenas, 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.

279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.