AI agents use settings_update 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 creates or modifies data reversibly (update), falling under the Write category. Severity is high because VPN panel settings control critical infrastructure—misuse could alter security policies, access controls, or service parameters affecting all users. However, it is not Destructive (reversible) and not Financial.
From the tool's definition Tool name 'settings_update' and description 'Update Remnawave panel settings' indicate modification of configuration data. The tool modifies panel settings, which is a reversible write operation on a VPN management system.
Documented attack patterns abuse exactly the kind of access settings_update 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 settings_update:
{
"version": "1",
"default": "deny",
"tools": {
"settings_update": {
"limits": [
{
"counter": "settings_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}settings_update 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.
Update Remnawave panel settings. 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 settings_update: 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.
settings_update 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 settings_update 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 settings_update. 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.
settings_update 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.