getSsidsBySite

Get a flat SSID list filtered by device type. Returns all SSIDs configured on the site for the specified device category (AP, wireless router, or both).

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/getssidsbysite.md

WHAT IT DOES

What getSsidsBySite does on Tplink Omada

AI agents call getSsidsBySite 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 getSsidsBySite is rated Low

This tool retrieves network configuration data (SSID list) without side effects. It queries existing SSIDs by site and device type, which is a read-only operation. While SSIDs are network-adjacent information that could inform reconnaissance, the tool itself performs no state changes, execution, or destructive actions.

From the tool's definition Tool name 'getSsidsBySite' and description indicate data retrieval: 'Get a flat SSID list filtered by device type. Returns all SSIDs configured on the site...' Uses passive 'Get' and 'Returns' language with no modification, deletion, or execution verbs.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

getSsidsBySite Allowed

getSsidsBySite 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": {
    "getSsidsBySite": {}
  }
}

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 getSsidsBySite call is checked against it from then on.

FAQ

Questions about getSsidsBySite

What does the getSsidsBySite tool do? +

Get a flat SSID list filtered by device type. Returns all SSIDs configured on the site for the specified device category (AP, wireless router, or both). 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 getSsidsBySite? +

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

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

Can I rate-limit getSsidsBySite? +

Yes. Add a rate_limit block to the getSsidsBySite 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 getSsidsBySite completely? +

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

getSsidsBySite 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 →