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