Get subscription info by short UUID (public endpoint)
AI agents call subscription_info 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 subscription information without modifying, deleting, or executing operations. It is explicitly marked as a public endpoint for querying, making it a Read category tool. The severity is low because subscription info retrieval has minimal blast radius—an AI agent accessing this would only be able to view existing subscription data, not alter VPN infrastructure or financial records.
From the tool's definition Tool name 'subscription_info' and description 'Get subscription info by short UUID (public endpoint)' indicate a data retrieval operation. The use of 'public endpoint' confirms this is a read-only query without side effects.
Documented attack patterns abuse exactly the kind of access subscription_info 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 subscription_info:
{
"version": "1",
"default": "deny",
"tools": {
"subscription_info": {}
}
}subscription_info 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 subscription info by short UUID (public endpoint). 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 subscription_info: 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.
subscription_info 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 subscription_info 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 subscription_info. 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.
subscription_info 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.