unifi_update_vpn_client_state
Enable or disable a specific VPN client by ID.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-update-vpn-client-state.md
What unifi_update_vpn_client_state does on UniFi Access MCP
AI agents invoke unifi_update_vpn_client_state to trigger actions in UniFi Access 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.
Why unifi_update_vpn_client_state is rated High
Enabling or disabling a VPN client changes the network connectivity state of a device, which is an external operational action with significant security implications. It is not a simple data write but an execution of a state change on network infrastructure. Misuse could cut off or expose network access.
From the tool's definition 'Enable or disable a specific VPN client by ID' — triggers an external network operation changing the operational state of a VPN client
Attacks that exploit this kind of access
The rule that runs unifi_update_vpn_client_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UniFi Access MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unifi_update_vpn_client_state, this is the rule to start with:
unifi_update_vpn_client_state stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every unifi_update_vpn_client_state call is checked against it from then on.
Questions about unifi_update_vpn_client_state
Enable or disable a specific VPN client by ID. It is categorised as a Execute tool in the UniFi Access MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the UniFi Access MCP server in PolicyLayer and add a rule for unifi_update_vpn_client_state: 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 UniFi Access MCP. Nothing to install.
unifi_update_vpn_client_state 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 unifi_update_vpn_client_state 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 unifi_update_vpn_client_state. 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.
unifi_update_vpn_client_state is provided by the UniFi Access MCP server (pypi:unifi-protect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UniFi Access, and thousands of servers like it.
Across the catalogue