getGlobalSecuritySetting
[DEPRECATED] Use getThreatList instead. Same threat-management endpoint. Name was misleading. Get the global security threat management list from the controller. Returns detected threats across all sites with severity, type, and timing details.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getglobalsecuritysetting.md
What getGlobalSecuritySetting does on Tplink Omada
AI agents call getGlobalSecuritySetting 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 getGlobalSecuritySetting is rated Low
This is a read-only operation that retrieves security threat information from the Omada controller. While the data returned (detected threats, severity, timing) could be sensitive and useful for reconnaissance, the tool performs no write, execute, or destructive operations.
From the tool's definition Tool retrieves and queries threat management data: 'Get the global security threat management list from the controller.
Attacks that exploit this kind of access
The rule that runs getGlobalSecuritySetting 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 getGlobalSecuritySetting, this is the rule to start with:
getGlobalSecuritySetting 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 getGlobalSecuritySetting call is checked against it from then on.
Questions about getGlobalSecuritySetting
[DEPRECATED] Use getThreatList instead. Same threat-management endpoint. Name was misleading. Get the global security threat management list from the controller. Returns detected threats across all sites with severity, type, and timing details. 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 getGlobalSecuritySetting: 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.
getGlobalSecuritySetting 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 getGlobalSecuritySetting 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 getGlobalSecuritySetting. 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.
getGlobalSecuritySetting 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