AI agents call validate_dns_record to retrieve information from Vultr Dns without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs input validation and checking of DNS record parameters prior to creation. It retrieves or queries the state of parameters without modifying any data or triggering external operations. This is a pre-flight check operation with no side effects, fitting the Read category. Severity is low because misuse cannot cause harm—validation failures simply prevent invalid requests.
From the tool's definition Tool name and description indicate validation/checking of DNS record parameters: 'Validate DNS record parameters before creation'. No modifications, deletions, or executions occur; only parameter inspection and validation.
Attacks that exploit this kind of access
Validate DNS record parameters before creation. It is categorised as a Read tool in the Vultr Dns MCP Server, which means it retrieves data without modifying state.
Register the Vultr Dns MCP server in PolicyLayer and add a rule for validate_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 Vultr Dns. Nothing to install.
validate_dns_record 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 validate_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 validate_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.
validate_dns_record is provided by the Vultr Dns MCP server (rsp2k/vultr-dns-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 →