Create a new boot environment by cloning an existing one. Useful for creating a restore point before updates.
AI agents use bootenv_create 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.
This tool creates a new data structure (boot environment) by cloning from an existing one. While boot environments are critical system components, the action is fundamentally a Write operation: it creates new data without permanently destroying anything.
From the tool's definition Tool name 'bootenv_create' and description states 'Create a new boot environment by cloning an existing one.' The action is creational and reversible—a new boot environment can be deleted if needed.
Documented attack patterns abuse exactly the kind of access bootenv_create 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 bootenv_create:
{
"version": "1",
"default": "deny",
"tools": {
"bootenv_create": {
"limits": [
{
"counter": "bootenv_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bootenv_create 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.
Create a new boot environment by cloning an existing one. Useful for creating a restore point before updates. 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 bootenv_create: 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.
bootenv_create 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 bootenv_create 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 bootenv_create. 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.
bootenv_create 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.