Get the DNS records that need to be configured for a domain. Returns MX, SPF, DKIM, and DMARC requirements.
AI agents call get_dns_requirements to retrieve information from TrekMail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns DNS configuration information needed for email setup. It performs a query operation with no side effects—it does not create, modify, delete, or execute any infrastructure changes. The action is purely informational, making it a Read category tool with low severity as misuse would only expose configuration details.
From the tool's definition Tool name 'get_dns_requirements' and description 'Get the DNS records... Returns MX, SPF, DKIM, and DMARC requirements' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
Get the DNS records that need to be configured for a domain. Returns MX, SPF, DKIM, and DMARC requirements. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for get_dns_requirements: 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 TrekMail MCP Server. Nothing to install.
get_dns_requirements 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 get_dns_requirements 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 get_dns_requirements. 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.
get_dns_requirements is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). 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 →