Low Risk

boot_state

Get the current state of the boot pool, including disk layout, health status, and capacity.

How to control boot_state ↓

What boot_state does on Truenas

AI agents call boot_state to retrieve information from Truenas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why boot_state needs a policy

This tool only retrieves information about the boot pool's state (disk layout, health, capacity). It has no side effects and performs no modifications.

From the tool's definition Get the current state of the boot pool, including disk layout, health status, and capacity.

Documented attack patterns abuse exactly the kind of access boot_state gives an agent:

How to control boot_state

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 boot_state:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "boot_state": {}
  }
}

boot_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Truenas — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about boot_state

What does the boot_state tool do? +

Get the current state of the boot pool, including disk layout, health status, and capacity. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on boot_state? +

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

boot_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit boot_state? +

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

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

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

Enforce policy on every Truenas tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.