Get detailed configuration for a specific client-to-site VPN server by ID, including protocol, port, authentication type, and allowed client settings.
AI agents call getClientToSiteVpnServerInfo to retrieve information from Tplink Omada without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves VPN server configuration data (protocol, port, authentication type, client settings) without altering state. It is a Read operation. Severity is medium because VPN configuration details, while not directly actionable, could leak security-sensitive information (authentication methods, ports, allowed client policies) that an attacker could use for reconnaissance or to plan network attacks.
From the tool's definition Tool name includes 'get' and description explicitly states it retrieves 'detailed configuration' for a VPN server, indicating query-only access to existing settings without modification.
Documented attack patterns abuse exactly the kind of access getClientToSiteVpnServerInfo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tplink Omada, and nothing reaches the server without passing your rules. This is the rule we recommend for getClientToSiteVpnServerInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getClientToSiteVpnServerInfo": {}
}
}getClientToSiteVpnServerInfo 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.
Get detailed configuration for a specific client-to-site VPN server by ID, including protocol, port, authentication type, and allowed client settings. 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 getClientToSiteVpnServerInfo: 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.
getClientToSiteVpnServerInfo 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 getClientToSiteVpnServerInfo 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 getClientToSiteVpnServerInfo. 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.
getClientToSiteVpnServerInfo 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.
Start from Tplink Omada, 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.
327 Tplink Omada tools catalogued and risk-classified — across an index of 43,000+ MCP servers.