This record as markdown: /tools/spranab-truenas-mcp/replication-update.md
What replication_update does on Truenas
AI agents use replication_update 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.
Why replication_update is rated Medium
This tool modifies an existing replication task configuration, which could alter backup/recovery schedules, target destinations, or data transfer parameters. While reversible (hence Write rather than Destructive), misconfiguration could redirect backups to wrong locations, skip critical data, or interfere with disaster recovery capabilities.
From the tool's definition Tool name 'replication_update' and description 'Update an existing replication task' indicate modification of a replication configuration. Replication tasks manage data synchronization/backup operations in TrueNAS SCALE.
Attacks that exploit this kind of access
The rule that runs replication_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For replication_update, this is the rule to start with:
replication_update 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every replication_update call is checked against it from then on.
Questions about replication_update
Update an existing replication 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.
Register the Truenas MCP server in PolicyLayer and add a rule for replication_update: 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.
replication_update 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 replication_update 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 replication_update. 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.
replication_update 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.
More on Truenas, and thousands of servers like it.
This server
Across the catalogue