pool_create
Create a new storage pool (destructive operation — requires confirm)
This record as markdown: /tools/spranab-truenas-mcp/pool-create.md
What pool_create does on Truenas
AI agents use pool_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.
Why pool_create is rated Medium
While creating a new pool is primarily a Write operation (it creates new data structures), the description notes it is 'destructive' — likely because pool creation can wipe/consume disks. However, the primary action is creating a new pool, not deleting existing data.
From the tool's definition Create a new storage pool (destructive operation — requires confirm)
Attacks that exploit this kind of access
The rule that runs pool_create 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 pool_create, this is the rule to start with:
pool_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every pool_create call is checked against it from then on.
Questions about pool_create
Create a new storage pool (destructive operation — requires confirm). 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 pool_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.
pool_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 pool_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 pool_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.
pool_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.
More on Truenas, and thousands of servers like it.
This server
Across the catalogue