getDscpConfig

[DEPRECATED] Get DSCP/QoS tag outbound traffic configuration. This is an alias for getQosPolicy — use getQosPolicy instead.

SERVERTplink Omada SOURCEmigueltvms/tplink-omada-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/migueltvms-tplink-omada-mcp/getdscpconfig.md

WHAT IT DOES

What getDscpConfig does on Tplink Omada

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

RISK

Why getDscpConfig is rated Low

This tool retrieves QoS configuration data without modifying, executing, or deleting anything. It is a straightforward query operation that returns existing configuration state. The deprecation status does not change its security category. Read operations have low severity since they only expose information without side effects.

From the tool's definition Tool name is 'getDscpConfig' and description states it 'Get[s] DSCP/QoS tag outbound traffic configuration'. The verb 'Get' and lack of any modification, deletion, or execution language indicate a read-only retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getDscpConfig 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 getDscpConfig, this is the rule to start with:

getDscpConfig Allowed

getDscpConfig is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getDscpConfig": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every getDscpConfig call is checked against it from then on.

FAQ

Questions about getDscpConfig

What does the getDscpConfig tool do? +

[DEPRECATED] Get DSCP/QoS tag outbound traffic configuration. 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 getDscpConfig? +

Register the Tplink Omada MCP server in PolicyLayer and add a rule for getDscpConfig: 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 getDscpConfig? +

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

Can I rate-limit getDscpConfig? +

Yes. Add a rate_limit block to the getDscpConfig 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 getDscpConfig completely? +

Set action: deny in the PolicyLayer policy for getDscpConfig. 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 getDscpConfig? +

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

KEEP EXPLORING

More on Tplink Omada, and thousands of servers like it.

This server

All 327 Tplink Omada tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →