Add a new user to the Ludus system. Args: username: Username for the new user password: Password for the new user is_admin: Whether the user should have admin privileges proxmox_username: Optional Proxmox username for the user email: Email address (required for Ludus 2.0) Returns: Created user in...
AI agents use add_user to create or update resources in Ludus FastMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ludus FastMCP environment.
This tool creates new user accounts and can assign administrative privileges to those accounts. While reversible (users can be deleted), it represents a Write operation that modifies system state by adding principals with potential elevated access. The ability to create admin users elevates severity to 'high' due to potential for privilege escalation and unauthorized access if misused by an AI agent.
From the tool's definition Tool description states 'Add a new user to the Ludus system' with parameters for username, password, is_admin privileges, and email. This creates new user accounts and can grant admin privileges.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access add_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ludus FastMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_user:
{
"version": "1",
"default": "deny",
"tools": {
"add_user": {
"limits": [
{
"counter": "add_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_user 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.
Add a new user to the Ludus system. Args: username: Username for the new user password: Password for the new user is_admin: Whether the user should have admin privileges proxmox_username: Optional Proxmox username for the user email: Email address (required for Ludus 2.0) Returns: Created user information. It is categorised as a Write tool in the Ludus FastMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for add_user: 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 Ludus FastMCP. Nothing to install.
add_user 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 add_user 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 add_user. 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.
add_user is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.