AI agents use users_create to create or update resources in Remnawave — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remnawave environment.
Creating a new VPN user is a reversible write operation—users can be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium rather than high because while it adds a user account, the blast radius depends on the account's permissions and the VPN's access controls; a single user creation is less critical than bulk operations or destructive actions.
From the tool's definition Tool name 'users_create' and description 'Create a new VPN user in Remnawave' indicate creation of new data in the VPN system. This is a write operation that modifies system state by adding a new user account.
Documented attack patterns abuse exactly the kind of access users_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Remnawave, and nothing reaches the server without passing your rules. This is the rule we recommend for users_create:
{
"version": "1",
"default": "deny",
"tools": {
"users_create": {
"limits": [
{
"counter": "users_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}users_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 VPN user in Remnawave. It is categorised as a Write tool in the Remnawave MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remnawave MCP server in PolicyLayer and add a rule for users_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 Remnawave. Nothing to install.
users_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 users_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 users_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.
users_create is provided by the Remnawave MCP server (trackline/mcp-remnawave). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 153 Remnawave tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
153 Remnawave tools catalogued and risk-classified — across an index of 42,500+ MCP servers.