Drop active connections for specified IPs
AI agents invoke ip_control_drop_connections to trigger actions in Remnawave. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool forcibly terminates active network connections for specified IP addresses. This is an Execute-level action as it triggers an external operation (dropping connections) with immediate real-world effects. It is not Destructive in the data-deletion sense, but it can disrupt active VPN sessions for users. Misuse by an AI agent could cause denial of service for legitimate users, hence high severity.
From the tool's definition 'Drop active connections for specified IPs' — actively terminates live network connections
Documented attack patterns abuse exactly the kind of access ip_control_drop_connections 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 ip_control_drop_connections:
{
"version": "1",
"default": "deny",
"tools": {
"ip_control_drop_connections": {
"limits": [
{
"counter": "ip_control_drop_connections_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ip_control_drop_connections stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Drop active connections for specified IPs. It is categorised as a Execute tool in the Remnawave MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Remnawave MCP server in PolicyLayer and add a rule for ip_control_drop_connections: 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.
ip_control_drop_connections is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ip_control_drop_connections 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 ip_control_drop_connections. 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.
ip_control_drop_connections 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.