Check VPN connection status — shows current IP, location, and whether traffic is routed through ProtonVPN
AI agents call vpn__status to retrieve information from Proton-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays status information (IP, location, routing status) about the VPN connection. It performs no modifications, does not execute commands with variable effects, does not delete data, and does not involve financial transactions. It is a pure information-retrieval operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'vpn__status' and description 'Check VPN connection status — shows current IP, location, and whether traffic is routed through ProtonVPN' indicate a query operation that retrieves state information without modification or side effects.
Documented attack patterns abuse exactly the kind of access vpn__status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proton-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for vpn__status:
{
"version": "1",
"default": "deny",
"tools": {
"vpn__status": {}
}
}vpn__status 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.
Check VPN connection status — shows current IP, location, and whether traffic is routed through ProtonVPN. It is categorised as a Read tool in the Proton-MCP MCP Server, which means it retrieves data without modifying state.
Register the Proton- MCP server in PolicyLayer and add a rule for vpn__status: 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 Proton-MCP. Nothing to install.
vpn__status 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 vpn__status 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 vpn__status. 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.
vpn__status is provided by the Proton- MCP server (jorgenclaw/proton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proton-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Proton-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.