Run an rsync task immediately
AI agents invoke rsync_task_run to trigger actions in Truenas. 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.
This tool executes an external operation (rsync) that transfers data between systems. While rsync itself is not inherently destructive, it is an Execute category tool because it runs external commands whose effects are determined by the task's configuration parameters.
From the tool's definition Tool name 'rsync_task_run' explicitly performs 'Run an rsync task immediately'. Rsync execution is a network data transfer operation that triggers external system operations whose effects depend on task configuration arguments (source, destination, filters,…
Documented attack patterns abuse exactly the kind of access rsync_task_run 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 rsync_task_run:
{
"version": "1",
"default": "deny",
"tools": {
"rsync_task_run": {
"limits": [
{
"counter": "rsync_task_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} rsync_task_run 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.
Free to start. No card required.
Run an rsync task immediately. It is categorised as a Execute tool in the Truenas MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Truenas MCP server in PolicyLayer and add a rule for rsync_task_run: 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.
rsync_task_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rsync_task_run 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 rsync_task_run. 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.
rsync_task_run 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.