AI agents use config_profiles_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 modifies existing configuration data (update operation), making it a Write category tool rather than Read, Execute, or Destructive. However, severity is high rather than medium because misuse could disrupt VPN service for multiple users through altered profiles. The confidence is high given the clear update semantics and VPN infrastructure context, though the exact scope of impact (single profile vs.
From the tool's definition Tool name 'config_profiles_update' combined with description 'Update a config profile' explicitly performs a modification operation.
Documented attack patterns abuse exactly the kind of access config_profiles_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 config_profiles_update:
{
"version": "1",
"default": "deny",
"tools": {
"config_profiles_update": {
"limits": [
{
"counter": "config_profiles_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}config_profiles_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 a config profile. 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 config_profiles_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.
config_profiles_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 config_profiles_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 config_profiles_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.
config_profiles_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.