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).
AI agents call getSsidsBySite 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 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.
Documented attack patterns abuse exactly the kind of access getSsidsBySite 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 getSsidsBySite:
{
"version": "1",
"default": "deny",
"tools": {
"getSsidsBySite": {}
}
}getSsidsBySite 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 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.
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.
getSsidsBySite 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 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.
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.
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.
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.