This record as markdown: /tools/mcp-control-plane/dns-settings.md
What dns_settings does on Mcp Control Plane
AI agents call dns_settings to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dns_settings is rated Low
This tool reads and returns DNS configuration information. It has no side effects, does not modify system state, and does not execute commands or delete data. It is a straightforward information retrieval operation, classified as Read with low severity since DNS settings are typically not sensitive security information and retrieval poses minimal risk.
From the tool's definition Tool name 'dns_settings' and description 'Return DNS settings' indicate a query operation that retrieves configuration data without modification.
Attacks that exploit this kind of access
The rule that runs dns_settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dns_settings, this is the rule to start with:
dns_settings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every dns_settings call is checked against it from then on.
Questions about dns_settings
Return DNS settings. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for dns_settings: 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 Mcp Control Plane. Nothing to install.
dns_settings 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 dns_settings 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 dns_settings. 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.
dns_settings is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue