getLanDnsRules

Get LAN DNS rules configured for 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/getlandnsrules.md

WHAT IT DOES

What getLanDnsRules does on Tplink Omada

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

This tool retrieves DNS rule configuration data from the TP-Link Omada controller. It performs a query operation ('Get') that does not create, modify, delete, or execute any actions—only reads existing configuration. The low severity reflects minimal blast radius if misused by an AI agent, as reading DNS rules poses no direct harm.

From the tool's definition Tool name 'getLanDnsRules' and description 'Get LAN DNS rules configured for the site' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

getLanDnsRules Allowed

getLanDnsRules 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": {
    "getLanDnsRules": {}
  }
}

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 getLanDnsRules call is checked against it from then on.

FAQ

Questions about getLanDnsRules

What does the getLanDnsRules tool do? +

Get LAN DNS rules configured for 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 getLanDnsRules? +

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

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

Can I rate-limit getLanDnsRules? +

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

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

getLanDnsRules 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 →