Get DNS cache setting for the site gateway. Shows whether DNS caching is enabled and the cache TTL configuration.
AI agents call getDnsCacheSetting 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.
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.
Documented attack patterns abuse exactly the kind of access getDnsCacheSetting gives an agent:
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 getDnsCacheSetting:
{
"version": "1",
"default": "deny",
"tools": {
"getDnsCacheSetting": {}
}
} getDnsCacheSetting is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
getDnsCacheSetting is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
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.