Get inbounds for a specific config profile
AI agents call config_profiles_get_inbounds 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 is a straightforward data retrieval operation that queries inbound configuration for a VPN profile. There are no side effects, no data modification, and no external operations triggered. The blast radius of misuse is minimal—an agent could only access existing configuration data, not alter or delete it. The context of VPN panel administration and the 'get' pattern confirm this is a Read category tool.
From the tool's definition Tool name 'config_profiles_get_inbounds' uses 'get' verb and description states 'Get inbounds for a specific config profile', indicating data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access config_profiles_get_inbounds 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 config_profiles_get_inbounds:
{
"version": "1",
"default": "deny",
"tools": {
"config_profiles_get_inbounds": {}
}
}config_profiles_get_inbounds 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 inbounds for a specific config profile. 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 config_profiles_get_inbounds: 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.
config_profiles_get_inbounds 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 config_profiles_get_inbounds 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 config_profiles_get_inbounds. 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.
config_profiles_get_inbounds 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.