util_dns_mx_priority_sort
DNS MX Priority Sort sorts MX exchanges by preference while preserving equal-priority order from bounded caller-supplied values without an external provider. Call DNS MX Priority Sort before choosing an MX exchange from caller-supplied preference records. Returns normalized web evidence, the comp...
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-dns-mx-priority-sort.md
What util_dns_mx_priority_sort does on Delx Mcp A2a
AI agents call util_dns_mx_priority_sort to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
records | array | Yes | Records supplied to DNS MX Priority Sort; used only for this bounded calculation and processed in memory without retention. |
Parameters from the server's own tool schema.
Why util_dns_mx_priority_sort is rated Low
Even though util_dns_mx_priority_sort only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs util_dns_mx_priority_sort safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_dns_mx_priority_sort, this is the rule to start with:
util_dns_mx_priority_sort 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 Delx Mcp A2a, apply this rule, and every util_dns_mx_priority_sort call is checked against it from then on.
Questions about util_dns_mx_priority_sort
DNS MX Priority Sort sorts MX exchanges by preference while preserving equal-priority order from bounded caller-supplied values without an external provider. Call DNS MX Priority Sort before choosing an MX exchange from caller-supplied preference records. Returns normalized web evidence, the computed finding, and an explicit pass or advisory status for DNS MX Priority Sort as versioned deterministic JSON. Limitation: Evaluates only caller-supplied metadata; it performs no DNS lookup, HTTP request, web search, credential use, or persistent storage. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_dns_mx_priority_sort accepts 1 parameter: records. Required: records. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_dns_mx_priority_sort: 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 Delx Mcp A2a. Nothing to install.
util_dns_mx_priority_sort 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 util_dns_mx_priority_sort 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 util_dns_mx_priority_sort. 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.
util_dns_mx_priority_sort is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue