Low Risk

listSiteToSiteVpns

List site-to-site VPN configurations: tunnel name, remote IP, status, protocol (IPsec/OpenVPN/WireGuard), and local/remote subnets.

How to control listSiteToSiteVpns ↓

What listSiteToSiteVpns does on Tplink Omada

AI agents call listSiteToSiteVpns 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.

Low Risk

Why listSiteToSiteVpns needs a policy

This is a read-only operation that retrieves sensitive network infrastructure details (VPN tunnels, IP addresses, subnets, protocols). While no data is modified, the severity is elevated to 'high' because exposing VPN configuration details to an AI agent could enable reconnaissance attacks, IP spoofing, or lateral movement planning if the agent is compromised or misaligned.

From the tool's definition The tool 'listSiteToSiteVpns' explicitly lists VPN configurations including tunnel names, IPs, status, protocols, and subnet information.

Documented attack patterns abuse exactly the kind of access listSiteToSiteVpns gives an agent:

How to control listSiteToSiteVpns

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 listSiteToSiteVpns:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "listSiteToSiteVpns": {}
  }
}

listSiteToSiteVpns is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tplink Omada — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about listSiteToSiteVpns

What does the listSiteToSiteVpns tool do? +

List site-to-site VPN configurations: tunnel name, remote IP, status, protocol (IPsec/OpenVPN/WireGuard), and local/remote subnets. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on listSiteToSiteVpns? +

Register the Tplink Omada MCP server in PolicyLayer and add a rule for listSiteToSiteVpns: 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.

What risk level is listSiteToSiteVpns? +

listSiteToSiteVpns is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit listSiteToSiteVpns? +

Yes. Add a rate_limit block to the listSiteToSiteVpns 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.

How do I block listSiteToSiteVpns completely? +

Set action: deny in the PolicyLayer policy for listSiteToSiteVpns. 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.

What MCP server provides listSiteToSiteVpns? +

listSiteToSiteVpns 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.

Enforce policy on every Tplink Omada tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.