listClientToSiteVpnClients
List all client-to-site VPN client configurations on the site.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/listclienttositevpnclients.md
What listClientToSiteVpnClients does on Tplink Omada
AI agents call listClientToSiteVpnClients 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 listClientToSiteVpnClients is rated Low
The tool performs a read-only operation that lists existing VPN client configurations without creating, modifying, deleting, or executing actions. The word 'list' combined with the passive 'List all...configurations' indicates data retrieval. Even though the server description mentions 'executing arbitrary Omada API calls,' this specific tool is scoped to listing only, making it a Read operation.
From the tool's definition Tool description states 'List all client-to-site VPN client configurations' which is a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs listClientToSiteVpnClients 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 listClientToSiteVpnClients, this is the rule to start with:
listClientToSiteVpnClients 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 listClientToSiteVpnClients call is checked against it from then on.
Questions about listClientToSiteVpnClients
List all client-to-site VPN client configurations on the site. 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 listClientToSiteVpnClients: 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.
listClientToSiteVpnClients 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 listClientToSiteVpnClients 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 listClientToSiteVpnClients. 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.
listClientToSiteVpnClients 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