This record as markdown: /tools/spranab-truenas-mcp/replication-restore.md
What replication_restore does on Truenas
AI agents use replication_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.
Why replication_restore is rated Medium
This tool restores data from a replication snapshot or backup, which is a reversible write operation that modifies the target system's data. While it overwrites existing data, restoration itself is a standard data recovery operation (not a permanent deletion).
From the tool's definition Tool name 'replication_restore' and description 'Restore from a replication task' indicate restoring data from a replication source, which modifies the current system state by overwriting/populating data.
Attacks that exploit this kind of access
The rule that runs replication_restore 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_restore, this is the rule to start with:
replication_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every replication_restore call is checked against it from then on.
Questions about replication_restore
Restore from a 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_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.
replication_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 replication_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 replication_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.
replication_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.
More on Truenas, and thousands of servers like it.
This server
Across the catalogue