update_dns_record
Add or update DNS records for a domain
This record as markdown: /tools/cbrown35-20i-mcp/update-dns-record.md
What update_dns_record does on 20i MCP Server
AI agents use update_dns_record to create or update resources in 20i MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 20i MCP Server environment.
Why update_dns_record is rated Medium
DNS record updates are Write operations because they modify domain configuration data reversibly (records can be changed back or deleted). However, severity is high because misconfigured DNS records can cause service outages, email delivery failures, or enable domain hijacking if an attacker gains control.
From the tool's definition Tool performs 'Add or update DNS records' - a reversible modification operation that creates or changes data. The verb 'update' combined with DNS record management indicates write capability.
Attacks that exploit this kind of access
The rule that runs update_dns_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_dns_record, this is the rule to start with:
update_dns_record stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every update_dns_record call is checked against it from then on.
Questions about update_dns_record
Add or update DNS records for a domain. It is categorised as a Write tool in the 20i MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for update_dns_record: 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 20i MCP Server. Nothing to install.
update_dns_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_dns_record 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 update_dns_record. 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.
update_dns_record is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue