AI agents use sub_page_configs_clone to create or update resources in Remnawave — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remnawave environment.
Cloning creates a new copy of an existing configuration, which is a reversible write operation. It does not delete or overwrite existing data, and has no financial implications. The blast radius is medium since it creates new configuration entries that could affect subscription page behavior.
From the tool's definition Clone a subscription page configuration
Documented attack patterns abuse exactly the kind of access sub_page_configs_clone 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 sub_page_configs_clone:
{
"version": "1",
"default": "deny",
"tools": {
"sub_page_configs_clone": {
"limits": [
{
"counter": "sub_page_configs_clone_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sub_page_configs_clone stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Clone a subscription page configuration. It is categorised as a Write tool in the Remnawave MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remnawave MCP server in PolicyLayer and add a rule for sub_page_configs_clone: 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.
sub_page_configs_clone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sub_page_configs_clone 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 sub_page_configs_clone. 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.
sub_page_configs_clone 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.