[DEPRECATED] Get gateway QoS policy settings. This is an alias for getQosPolicy — use getQosPolicy instead.
AI agents call getQosPolicyRule 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 is a read-only retrieval operation that queries QoS (Quality of Service) policy configuration data from the TP-Link Omada controller. It performs no side effects, creates no resources, executes no commands, and makes no modifications. The deprecation note and alias reference do not change its functional classification. Network configuration inspection poses minimal risk compared to other tool categories.
From the tool's definition Tool name 'getQosPolicyRule' with verb 'get' and description states it retrieves 'gateway QoS policy settings' with no modification or execution capability mentioned.
Documented attack patterns abuse exactly the kind of access getQosPolicyRule 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 getQosPolicyRule:
{
"version": "1",
"default": "deny",
"tools": {
"getQosPolicyRule": {}
}
} getQosPolicyRule 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.
[DEPRECATED] Get gateway QoS policy settings. This is an alias for getQosPolicy — use getQosPolicy instead. 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 getQosPolicyRule: 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.
getQosPolicyRule 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 getQosPolicyRule 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 getQosPolicyRule. 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.
getQosPolicyRule 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.