Unlock an encrypted dataset
AI agents use dataset_unlock 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.
Unlocking an encrypted dataset modifies the access state and security posture of that dataset, making it a Write operation rather than Read (which would be mere inspection). While not destructive (data is not deleted or overwritten) or financial, it is high-severity because unauthorized unlocking of encrypted data could expose sensitive information to an AI agent and enable subsequent malicious actions.
From the tool's definition Tool name 'dataset_unlock' and description 'Unlock an encrypted dataset' indicate a state-changing operation on encrypted storage.
Documented attack patterns abuse exactly the kind of access dataset_unlock 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 dataset_unlock:
{
"version": "1",
"default": "deny",
"tools": {
"dataset_unlock": {
"limits": [
{
"counter": "dataset_unlock_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}dataset_unlock 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.
Unlock an encrypted dataset. 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 dataset_unlock: 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.
dataset_unlock 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 dataset_unlock 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 dataset_unlock. 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.
dataset_unlock 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.