Bulk update squad assignments for selected users
AI agents use users_bulk_update_squads 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.
This tool modifies user squad assignments (reversible changes to user records). While 'bulk' operations on multiple users create broader impact than single-user writes, the changes are not destructive (not deleting users or data) and not financial.
From the tool's definition Tool name contains 'bulk_update' and description states 'Bulk update squad assignments for selected users', indicating modification of user properties at scale.
Documented attack patterns abuse exactly the kind of access users_bulk_update_squads 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_bulk_update_squads:
{
"version": "1",
"default": "deny",
"tools": {
"users_bulk_update_squads": {
"limits": [
{
"counter": "users_bulk_update_squads_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}users_bulk_update_squads 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.
Bulk update squad assignments for selected users. 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_bulk_update_squads: 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_bulk_update_squads 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_bulk_update_squads 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_bulk_update_squads. 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_bulk_update_squads 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.