Low Risk

getQosMarkingRule

[DEPRECATED] Get gateway QoS marking (tag outbound traffic) settings. This is an alias for getQosPolicy — use getQosPolicy instead.

How to control getQosMarkingRule ↓

What getQosMarkingRule does on Tplink Omada

AI agents call getQosMarkingRule 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.

Low Risk

Why getQosMarkingRule needs a policy

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.

Documented attack patterns abuse exactly the kind of access getQosMarkingRule gives an agent:

How to control getQosMarkingRule

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 getQosMarkingRule:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getQosMarkingRule": {}
  }
}

getQosMarkingRule is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tplink Omada — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getQosMarkingRule

What does the getQosMarkingRule tool do? +

[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.

How do I enforce a policy on getQosMarkingRule? +

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.

What risk level is getQosMarkingRule? +

getQosMarkingRule is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getQosMarkingRule? +

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.

How do I block getQosMarkingRule completely? +

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.

What MCP server provides getQosMarkingRule? +

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.

Enforce policy on every Tplink Omada tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.