New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

getWanQosConfig

Get QoS configuration for gateway WAN ports on the site.

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/getwanqosconfig.md

What getWanQosConfig does on Tplink Omada

AI agents call getWanQosConfig 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 getWanQosConfig is rated Low

This tool queries and retrieves QoS (Quality of Service) configuration data from gateway WAN ports. The 'get' verb and description indicate a read-only operation that does not modify, delete, or execute any actions. While the parent server can execute arbitrary API calls, this specific tool is limited to configuration retrieval.

From the tool's definition Tool name contains 'get' prefix and description states 'Get QoS configuration' — a retrieval operation with no modification or side effects.

Questions about getWanQosConfig

What does the getWanQosConfig tool do? +

Get QoS configuration for gateway WAN ports on the site. 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 getWanQosConfig? +

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

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

Can I rate-limit getWanQosConfig? +

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tplink Omada's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.