AI agents call subscriptions_get_subpage_config 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 configuration data for a subscription page without modifying, deleting, or executing operations. The 'get' verb and read-only nature of retrieving page configuration clearly places it in the Read category. The low severity reflects that configuration retrieval poses minimal risk even if accessed by an unauthorized agent.
From the tool's definition Tool name contains 'get' and description states 'Get subscription page configuration', indicating data retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access subscriptions_get_subpage_config 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_subpage_config:
{
"version": "1",
"default": "deny",
"tools": {
"subscriptions_get_subpage_config": {}
}
}subscriptions_get_subpage_config 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 page configuration. 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_subpage_config: 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_subpage_config 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_subpage_config 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_subpage_config. 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_subpage_config 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.