list_vpn_tunnel
AI agents call list_vpn_tunnel to retrieve information from VPN As A Service MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'list' universally indicates data retrieval without modification or side effects. Given the VPN management context and consistent naming with other read-only sibling tools (get_*, list_*), this is classified as Read. Severity is low because querying tunnel information poses minimal risk—no infrastructure changes, deletions, or financial impact.
From the tool's definition Tool name 'list_vpn_tunnel' suggests enumeration/retrieval of VPN tunnel data. Description is empty, but sibling tools like 'list_available_vpn' and 'get_status' are read operations, indicating this follows the same pattern.
Attacks that exploit this kind of access
list_vpn_tunnel. It is categorised as a Read tool in the VPN As A Service MCP MCP Server, which means it retrieves data without modifying state.
Register the VPN As A Service MCP server in PolicyLayer and add a rule for list_vpn_tunnel: 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 VPN As A Service MCP. Nothing to install.
list_vpn_tunnel 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 list_vpn_tunnel 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 list_vpn_tunnel. 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.
list_vpn_tunnel is provided by the VPN As A Service MCP server (nolaan/ai_vpn_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →