Get result of an IP fetch job
AI agents call ip_control_get_fetch_ips_result 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.
This tool retrieves the outcome of a previously initiated IP fetch operation. It performs no modifications, deletions, or external operations—it merely reads and returns cached or stored results from an asynchronous job. This is consistent with Read category semantics (query, get, fetch).
From the tool's definition Tool name contains 'get' and 'fetch_result'; description uses 'Get result' which indicates data retrieval only. The action is polling/querying the status of a completed background job without side effects.
Documented attack patterns abuse exactly the kind of access ip_control_get_fetch_ips_result 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_get_fetch_ips_result:
{
"version": "1",
"default": "deny",
"tools": {
"ip_control_get_fetch_ips_result": {}
}
}ip_control_get_fetch_ips_result 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.
Get result of an IP fetch 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_get_fetch_ips_result: 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_get_fetch_ips_result 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_get_fetch_ips_result 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_get_fetch_ips_result. 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_get_fetch_ips_result 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.
Start from Remnawave, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
153 Remnawave tools catalogued and risk-classified — across an index of 43,000+ MCP servers.