AI agents call subscriptions_get_by_short_uuid 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 based on a short UUID identifier. As a 'get' operation, it performs a read-only query with no side effects. However, severity is elevated to 'medium' rather than 'low' because subscription details may contain sensitive information (billing status, payment methods, service entitlements, user association) that could be misused if an agent queries subscriptions…
From the tool's definition Tool name 'subscriptions_get_by_short_uuid' and description 'Get subscription details by short UUID' indicate a retrieval operation with no modification or deletion.
Documented attack patterns abuse exactly the kind of access subscriptions_get_by_short_uuid 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 subscriptions_get_by_short_uuid:
{
"version": "1",
"default": "deny",
"tools": {
"subscriptions_get_by_short_uuid": {}
}
}subscriptions_get_by_short_uuid 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 details by short UUID. 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 subscriptions_get_by_short_uuid: 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.
subscriptions_get_by_short_uuid 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 subscriptions_get_by_short_uuid 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 subscriptions_get_by_short_uuid. 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.
subscriptions_get_by_short_uuid 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.