Get the global threat count grouped by severity level (critical, high, medium, low) within a time range. Provides a summary view of the current threat landscape across all sites. Requires startTime and endTime as Unix epoch seconds.
AI agents call getThreatCount 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 aggregated threat statistics for monitoring and reporting purposes. It queries existing threat data without side effects, modification, or any capability to change system state or security posture. The low severity reflects that misuse would only result in information disclosure, not operational impact.
From the tool's definition Tool description states 'Get the global threat count grouped by severity level' and 'Provides a summary view' — these are retrieval and query operations with no modification, creation, or deletion of data.
Documented attack patterns abuse exactly the kind of access getThreatCount 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 getThreatCount:
{
"version": "1",
"default": "deny",
"tools": {
"getThreatCount": {}
}
}getThreatCount 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 the global threat count grouped by severity level (critical, high, medium, low) within a time range. Provides a summary view of the current threat landscape across all sites. Requires startTime and endTime as Unix epoch seconds. 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 getThreatCount: 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.
getThreatCount 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 getThreatCount 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 getThreatCount. 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.
getThreatCount 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.