getQosMarkingRule
[DEPRECATED] Get gateway QoS marking (tag outbound traffic) settings. This is an alias for getQosPolicy — use getQosPolicy instead.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getqosmarkingrule.md
What getQosMarkingRule does on Tplink Omada
AI agents call getQosMarkingRule 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 getQosMarkingRule is rated Low
This tool retrieves and queries QoS marking rule configuration from the TP-Link Omada controller without modifying any settings, executing code, or causing side effects. While QoS rules can affect network traffic shaping, merely reading their current state is a passive information retrieval operation with minimal blast radius if misused by an AI agent—worst case being information disclosure about network policies.
From the tool's definition Tool name 'getQosMarkingRule' and description 'Get gateway QoS marking settings' indicate a read-only retrieval operation with no modification or execution of commands. The tool queries existing QoS policy configuration.
Attacks that exploit this kind of access
The rule that runs getQosMarkingRule 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 getQosMarkingRule, this is the rule to start with:
getQosMarkingRule 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 getQosMarkingRule call is checked against it from then on.
Questions about getQosMarkingRule
[DEPRECATED] Get gateway QoS marking (tag outbound traffic) 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 getQosMarkingRule: 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.
getQosMarkingRule 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 getQosMarkingRule 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 getQosMarkingRule. 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.
getQosMarkingRule 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