AI agents call ip_control_fetch_ips to retrieve information from Remnawave without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves/queries active IP addresses associated with a user account. The use of 'fetch' and the read-only nature of querying existing IP data without modifying, deleting, or executing operations classifies this as a Read operation. While IPs could be considered sensitive information, the tool itself performs no destructive, financial, or executable actions.
From the tool's definition Tool name contains 'fetch' and description states 'Fetch active IPs for a user', indicating data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access ip_control_fetch_ips 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_fetch_ips:
{
"version": "1",
"default": "deny",
"tools": {
"ip_control_fetch_ips": {}
}
}ip_control_fetch_ips is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch active IPs for a user (async job). It is categorised as a Read tool in the Remnawave MCP Server, which means it retrieves data without modifying state.
Register the Remnawave MCP server in PolicyLayer and add a rule for ip_control_fetch_ips: 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_fetch_ips is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ip_control_fetch_ips 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_fetch_ips. 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_fetch_ips 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.