List alert logs across all sites on the controller: threshold breaches, device failures, security events, etc. Use startTime/endTime (both required if filtering by time) to narrow the range.
AI agents call listGlobalAlerts 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 and queries alert log information without side effects. It does not modify configuration, execute commands, delete data, or trigger external operations. While the TP-Link Omada server overall exposes APIs capable of executing arbitrary operations (per server description), this specific tool is limited to read-only access to alert logs.
From the tool's definition Tool name 'listGlobalAlerts' and description 'List alert logs across all sites' indicates retrieval of existing alert data with no modification, creation, deletion, or execution of commands. Parameters are time-range filters for querying.
Documented attack patterns abuse exactly the kind of access listGlobalAlerts 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 listGlobalAlerts:
{
"version": "1",
"default": "deny",
"tools": {
"listGlobalAlerts": {}
}
}listGlobalAlerts 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 across all sites on the controller: threshold breaches, device failures, security events, etc. 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 listGlobalAlerts: 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.
listGlobalAlerts 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 listGlobalAlerts 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 listGlobalAlerts. 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.
listGlobalAlerts 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.