listSiteAlerts
List alert logs for a site: threshold breaches, device failures, security events, and other conditions requiring attention. Returns alert type, severity, device, and timestamp. Use startTime/endTime (both required if filtering by time) to narrow the range.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/listsitealerts.md
What listSiteAlerts does on Tplink Omada
AI agents call listSiteAlerts 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 listSiteAlerts is rated Low
This tool retrieves historical alert and log data from the TP-Link Omada controller. While it is Read-category (no side effects), the severity is elevated to medium rather than low because alerts often contain security-relevant information (including 'security events'), device failures, and network conditions that could be sensitive.
From the tool's definition Tool description states it 'List alert logs for a site' and 'Returns alert type, severity, device, and timestamp' — purely a retrieval operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs listSiteAlerts 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 listSiteAlerts, this is the rule to start with:
listSiteAlerts 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 listSiteAlerts call is checked against it from then on.
Questions about listSiteAlerts
List alert logs for a site: threshold breaches, device failures, security events, and other conditions requiring attention. Returns alert type, severity, device, and timestamp. Use startTime/endTime (both required if filtering by time) to narrow the range. 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 listSiteAlerts: 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.
listSiteAlerts 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 listSiteAlerts 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 listSiteAlerts. 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.
listSiteAlerts 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