Set or change a user
AI agents use user_set_password 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 modifies user authentication credentials, which is a Write operation (reversible data modification). Severity is high because compromised password-setting capabilities could grant unauthorized access to TrueNAS accounts, though the operation itself is not destructive or financial. The confidence is high given the explicit nature of the tool name and description.
From the tool's definition Tool name 'user_set_password' and description 'Set or change a user' indicate modification of user account credentials. This is a write operation that creates or modifies data (password hashes/credentials) reversibly.
Documented attack patterns abuse exactly the kind of access user_set_password 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_set_password:
{
"version": "1",
"default": "deny",
"tools": {
"user_set_password": {
"limits": [
{
"counter": "user_set_password_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}user_set_password 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.
Set or change a user. 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_set_password: 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_set_password 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_set_password 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_set_password. 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_set_password 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.