dataset_lock

Lock an encrypted dataset

SERVERTruenas SOURCEspranab/truenas-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/spranab-truenas-mcp/dataset-lock.md

WHAT IT DOES

What dataset_lock does on Truenas

AI agents invoke dataset_lock 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.

RISK

Why dataset_lock is rated High

Locking an encrypted dataset is an operational action that makes data inaccessible (encrypts/locks it), which is a significant state change. While not permanently destructive (data can be unlocked), it can cause service disruptions and data unavailability. It triggers an external operation on the TrueNAS system that changes the accessibility state of the dataset.

From the tool's definition Lock an encrypted dataset

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dataset_lock 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 dataset_lock, this is the rule to start with:

dataset_lock Rate-limited

dataset_lock 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dataset_lock": {
      "limits": [
        {
          "counter": "dataset_lock_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every dataset_lock call is checked against it from then on.

FAQ

Questions about dataset_lock

What does the dataset_lock tool do? +

Lock an encrypted dataset. 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.

How do I enforce a policy on dataset_lock? +

Register the Truenas MCP server in PolicyLayer and add a rule for dataset_lock: 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.

What risk level is dataset_lock? +

dataset_lock is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dataset_lock? +

Yes. Add a rate_limit block to the dataset_lock 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.

How do I block dataset_lock completely? +

Set action: deny in the PolicyLayer policy for dataset_lock. 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.

What MCP server provides dataset_lock? +

dataset_lock 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.

KEEP EXPLORING

More on Truenas, and thousands of servers like it.

This server

All 279 Truenas tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →