run_smart_test · Truenas Ws MCP: Risk & Policy

WHAT IT DOES

What run_smart_test does on Truenas Ws

AI agents invoke run_smart_test to trigger actions in Truenas Ws. 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.

WHY IT NEEDS A POLICY

Why run_smart_test needs a policy

This tool triggers execution of hardware diagnostic operations on disks. While SMART tests are non-destructive read-only operations that examine disk health without modifying data, they are fundamentally Execute category because they initiate external system operations whose behavior depends on runtime arguments.

From the tool's definition Tool runs a SMART test on specified disks with configurable test_type (SHORT or LONG). 'Run' indicates execution of an external operation (hardware diagnostics) whose effects depend on the test_type argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_smart_test Rate-limited

run_smart_test 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": {
    "run_smart_test": {
      "limits": [
        {
          "counter": "run_smart_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Truenas Ws, so you can run agents against it safely.

FAQ

Questions about run_smart_test

What does the run_smart_test tool do? +

Run a SMART test on specified disks. test_type: SHORT or LONG. Note: TrueNAS 25.10 removed SMART scheduling from the API — these are manual tests only. It is categorised as a Execute tool in the Truenas Ws MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_smart_test? +

Register the Truenas Ws MCP server in PolicyLayer and add a rule for run_smart_test: 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 Ws. Nothing to install.

What risk level is run_smart_test? +

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

Can I rate-limit run_smart_test? +

Yes. Add a rate_limit block to the run_smart_test 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 run_smart_test completely? +

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

run_smart_test is provided by the Truenas Ws MCP server (thoriphes/truenas-ws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.