Start the VPN tunnel.
AI agents invoke start_vpn to trigger actions in VPN As A Service MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a command that activates VPN infrastructure and modifies network behavior. It is not a read operation (no data retrieval), not write in the reversible sense (it's closer to state change), and not destructive (the effect is reversible via stop_vpn). However, it runs an operation whose effects depend on the VPN configuration and infrastructure state, making it Execute-category.
From the tool's definition Tool 'start_vpn' initiates a VPN tunnel by performing an action that triggers external network operations.
Attacks that exploit this kind of access
Start the VPN tunnel. It is categorised as a Execute tool in the VPN As A Service MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the VPN As A Service MCP server in PolicyLayer and add a rule for start_vpn: 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.
start_vpn is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_vpn 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 start_vpn. 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.
start_vpn 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 →