Get connection keys for a subscription
AI agents call subscriptions_get_connection_keys 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 existing connection keys associated with a subscription. It performs a query/read action without modifying, deleting, or executing any operations. While connection keys could be sensitive, the tool itself only reads data; severity is low because obtaining keys is a standard read operation.
From the tool's definition Tool name 'subscriptions_get_connection_keys' uses the verb 'get', and description states 'Get connection keys for a subscription', which is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access subscriptions_get_connection_keys 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_connection_keys:
{
"version": "1",
"default": "deny",
"tools": {
"subscriptions_get_connection_keys": {}
}
}subscriptions_get_connection_keys 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 connection keys for a subscription. 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_connection_keys: 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_connection_keys 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_connection_keys 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_connection_keys. 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_connection_keys 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.