listSiteToSiteVpns

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

SERVERTplink Omada SOURCEmigueltvms/tplink-omada-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/migueltvms-tplink-omada-mcp/listsitetositevpns.md

WHAT IT DOES

What listSiteToSiteVpns does on Tplink Omada

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

RISK

Why listSiteToSiteVpns is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs listSiteToSiteVpns 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 listSiteToSiteVpns, this is the rule to start with:

listSiteToSiteVpns Allowed

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "listSiteToSiteVpns": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every listSiteToSiteVpns call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Tplink Omada, and thousands of servers like it.

This server

All 327 Tplink Omada tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →