Create a new DNS record
AI agents use create_dns_record to create or update resources in Domain Suite — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Domain Suite environment.
Creating DNS records modifies critical infrastructure that controls domain routing, mail delivery, and security settings. This is reversible (records can be deleted), so it does not qualify as Destructive. However, misuse could redirect traffic, enable phishing, intercept emails, or cause significant service disruption.
From the tool's definition Tool name is 'create_dns_record' and description states 'Create a new DNS record'. The verb 'create' indicates data modification. The server description mentions 'managing DNS records...
Attacks that exploit this kind of access
Create a new DNS record. It is categorised as a Write tool in the Domain Suite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Domain Suite MCP server in PolicyLayer and add a rule for create_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 Domain Suite. Nothing to install.
create_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 create_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 create_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.
create_dns_record is provided by the Domain Suite MCP server (oso95/domain-suite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →