AI agents use api_tokens_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 API tokens is a write operation that generates new authentication credentials. While reversible (tokens can be deleted), misuse could allow an AI agent to create credentials for unauthorized access to the VPN panel, escalating privileges or enabling lateral movement. The high severity reflects the security-sensitive nature of API token generation in an administrative context.
From the tool's definition Tool name 'api_tokens_create' and description 'Create a new API token' indicate creation of new API credentials.
Documented attack patterns abuse exactly the kind of access api_tokens_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 api_tokens_create:
{
"version": "1",
"default": "deny",
"tools": {
"api_tokens_create": {
"limits": [
{
"counter": "api_tokens_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}api_tokens_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 API token. 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 api_tokens_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.
api_tokens_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 api_tokens_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 api_tokens_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.
api_tokens_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.