Enable OpenVPN client interface (will attempt connection)
AI agents invoke mikrotik_enable_openvpn_client to trigger actions in MikroTik Cursor 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.
Enabling an OpenVPN client interface triggers an active network connection attempt to an external VPN endpoint. This is an operational action with external effects — it initiates a network tunnel, potentially routing traffic through a third-party server. It is not merely writing config data; it executes the connection. Misuse could redirect router traffic through malicious VPN endpoints, making severity high.
From the tool's definition Enable OpenVPN client interface (will attempt connection)
Attacks that exploit this kind of access
Enable OpenVPN client interface (will attempt connection). It is categorised as a Execute tool in the MikroTik Cursor MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_enable_openvpn_client: 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 MikroTik Cursor MCP. Nothing to install.
mikrotik_enable_openvpn_client 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 mikrotik_enable_openvpn_client 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 mikrotik_enable_openvpn_client. 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.
mikrotik_enable_openvpn_client is provided by the MikroTik Cursor MCP server (kevinpez/mikrotik-cursor-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 →