truenas_run_tests · TrueNAS Middleware MCP Server MCP

WHAT IT DOES

What truenas_run_tests does on TrueNAS Middleware MCP Server

AI agents invoke truenas_run_tests to trigger actions in TrueNAS Middleware MCP Server. 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 truenas_run_tests needs a policy

Running tests via Docker is an Execute operation because it triggers external processes whose side effects depend on arguments (which tests run, what they modify). While test execution is typically benign, it can access/modify the system under test, create temporary files, or trigger unintended side effects if tests are misconfigured.

From the tool's definition Tool name is 'truenas_run_tests' and description states 'Run TrueNAS middleware tests using Docker' — this executes code (tests) in a containerized environment, with effects dependent on which tests are run and what they target.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

truenas_run_tests Rate-limited

truenas_run_tests 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": {
    "truenas_run_tests": {
      "limits": [
        {
          "counter": "truenas_run_tests_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 Middleware MCP Server, so you can run agents against it safely.

FAQ

Questions about truenas_run_tests

What does the truenas_run_tests tool do? +

Run TrueNAS middleware tests using Docker. IMPORTANT: When using Code Claude, you MUST run. It is categorised as a Execute tool in the TrueNAS Middleware MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on truenas_run_tests? +

Register the TrueNAS Middleware MCP Server MCP server in PolicyLayer and add a rule for truenas_run_tests: 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 Middleware MCP Server. Nothing to install.

What risk level is truenas_run_tests? +

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

Can I rate-limit truenas_run_tests? +

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

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

truenas_run_tests is provided by the TrueNAS Middleware MCP Server MCP server (sonicaj/tn_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.