Create a new user account on the TrueNAS system.
AI agents use user_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.
Creating a user account modifies system state by adding a new user to the TrueNAS system. This is reversible (the account can be deleted), so it falls under Write rather than Destructive. However, the severity is high because an attacker could create privileged accounts to maintain persistence, escalate privileges, or grant unauthorized access to the system.
From the tool's definition Tool name 'user_create' and description 'Create a new user account on the TrueNAS system' indicate creation of a user account, which is a data modification action.
Documented attack patterns abuse exactly the kind of access user_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 user_create:
{
"version": "1",
"default": "deny",
"tools": {
"user_create": {
"limits": [
{
"counter": "user_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}user_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 user account on the TrueNAS system. 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 user_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.
user_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 user_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 user_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.
user_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.