Restore data from cloud to a local path
AI agents use cloudsync_restore 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.
This tool creates or modifies data on the local system by pulling data from cloud storage. While restoration is technically reversible (the original local data may be overwritten but the cloud source persists), the operation itself is a Write action that alters the local filesystem. It is not Destructive because the operation doesn't irreversibly delete data—it restores it.
From the tool's definition Tool name 'cloudsync_restore' and description 'Restore data from cloud to a local path' indicate the tool modifies local storage by writing/importing data from remote sources.
Documented attack patterns abuse exactly the kind of access cloudsync_restore gives an agent:
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_restore:
{
"version": "1",
"default": "deny",
"tools": {
"cloudsync_restore": {
"limits": [
{
"counter": "cloudsync_restore_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cloudsync_restore 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.
Free to start. No card required.
Restore data from cloud to a local path. 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.
Register the Truenas MCP server in PolicyLayer and add a rule for cloudsync_restore: 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.
cloudsync_restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cloudsync_restore 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.
Set action: deny in the PolicyLayer policy for cloudsync_restore. 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.
cloudsync_restore 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.
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.