get_dns_requirements

Get the DNS records that need to be configured for a domain. Returns SPF, DKIM and DMARC, plus MX when the domain

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/get-dns-requirements.md

WHAT IT DOES

What get_dns_requirements does on TrekMail MCP Server

AI agents call get_dns_requirements to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_dns_requirements is rated Low

Retrieves DNS configuration requirements without modifying infrastructure or exposing sensitive operations.

From the tool's definition Get the DNS records that need to be configured for a domain. Returns SPF, DKIM and DMARC, plus MX

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_dns_requirements safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dns_requirements, this is the rule to start with:

get_dns_requirements Allowed

get_dns_requirements is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dns_requirements": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every get_dns_requirements call is checked against it from then on.

FAQ

Questions about get_dns_requirements

What does the get_dns_requirements tool do? +

Get the DNS records that need to be configured for a domain. Returns SPF, DKIM and DMARC, plus MX when the domain. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dns_requirements? +

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.

What risk level is get_dns_requirements? +

get_dns_requirements is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_dns_requirements? +

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.

How do I block get_dns_requirements completely? +

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.

What MCP server provides get_dns_requirements? +

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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 285 TrekMail MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →