This record as markdown: /tools/migueltvms-tplink-omada-mcp/listsitesstacks.md
What listSitesStacks does on Tplink Omada
AI agents call listSitesStacks 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.
Why listSitesStacks is rated Low
This tool retrieves information about switch stacks within a site. It performs a read-only operation that queries existing data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could only enumerate network infrastructure details, which is a low-severity information disclosure risk.
From the tool's definition Tool name 'listSitesStacks' and description 'List switch stacks in a site' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs listSitesStacks 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 listSitesStacks, this is the rule to start with:
listSitesStacks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every listSitesStacks call is checked against it from then on.
Questions about listSitesStacks
List switch stacks in a site. 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 listSitesStacks: 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.
listSitesStacks 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 listSitesStacks 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 listSitesStacks. 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.
listSitesStacks 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.
More on Tplink Omada, and thousands of servers like it.
This server
Across the catalogue