getDnsCacheSetting

Get DNS cache setting for the site gateway. Shows whether DNS caching is enabled and the cache TTL configuration.

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

WHAT IT DOES

What getDnsCacheSetting does on Tplink Omada

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

This tool only retrieves existing DNS cache configuration settings for the site gateway. It does not modify, delete, execute commands, or move financial assets. The information returned (whether caching is enabled and TTL values) is purely informational and carries minimal risk if accessed by an AI agent. Classification as Read is appropriate.

From the tool's definition Tool name and description indicate it retrieves DNS cache settings ('Get DNS cache setting'). The action is to 'show' configuration, which is a read-only query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

getDnsCacheSetting Allowed

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

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

FAQ

Questions about getDnsCacheSetting

What does the getDnsCacheSetting tool do? +

Get DNS cache setting for the site gateway. Shows whether DNS caching is enabled and the cache TTL configuration. 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 getDnsCacheSetting? +

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

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

Can I rate-limit getDnsCacheSetting? +

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

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

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