getVpnUserList
Get the list of VPN users for a site (paginated), including username, assigned VPN server, and connection permissions.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getvpnuserlist.md
What getVpnUserList does on Tplink Omada
AI agents call getVpnUserList to retrieve information from Tplink Omada without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getVpnUserList is rated Low
This tool retrieves and lists VPN user information for a site. It performs a read-only query operation with no capability to modify, delete, or execute actions. While VPN user data could be sensitive, the tool itself is purely informational.
From the tool's definition Tool name 'getVpnUserList' and description 'Get the list of VPN users' indicate a retrieval operation that queries existing data without modification.
Attacks that exploit this kind of access
The rule that runs getVpnUserList safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tplink Omada, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getVpnUserList, this is the rule to start with:
getVpnUserList is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every getVpnUserList call is checked against it from then on.
Questions about getVpnUserList
Get the list of VPN users for a site (paginated), including username, assigned VPN server, and connection permissions. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.
Register the Tplink Omada MCP server in PolicyLayer and add a rule for getVpnUserList: 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 Tplink Omada. Nothing to install.
getVpnUserList 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 getVpnUserList 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 getVpnUserList. 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.
getVpnUserList is provided by the Tplink Omada MCP server (migueltvms/tplink-omada-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tplink Omada, and thousands of servers like it.
This server
Across the catalogue