reach_getProfileDomainDNSStatusV1
Retrieve the DNS configuration status for a profile's domain. This endpoint reports the state of MX, SPF, DKIM and DMARC records, including the actual records found and the suggested records required for correct email delivery.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-getprofiledomaindnsstatusv1.md
What reach_getProfileDomainDNSStatusV1 does on Hostinger Api
AI agents call reach_getProfileDomainDNSStatusV1 to retrieve information from Hostinger Api 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 |
|---|---|---|---|
profileUuid | string | Yes | Profile uuid parameter |
Parameters from the server's own tool schema.
Why reach_getProfileDomainDNSStatusV1 is rated Low
This tool performs a read-only query of DNS configuration status for a domain. It reports on MX, SPF, DKIM, and DMARC records and returns the actual vs. suggested configuration. There are no side effects, data modifications, or destructive operations.
From the tool's definition Tool name includes 'get' and description states 'Retrieve the DNS configuration status' and 'reports the state'. The function retrieves and reports existing DNS records without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs reach_getProfileDomainDNSStatusV1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reach_getProfileDomainDNSStatusV1, this is the rule to start with:
reach_getProfileDomainDNSStatusV1 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 Hostinger Api, apply this rule, and every reach_getProfileDomainDNSStatusV1 call is checked against it from then on.
Questions about reach_getProfileDomainDNSStatusV1
Retrieve the DNS configuration status for a profile's domain. This endpoint reports the state of MX, SPF, DKIM and DMARC records, including the actual records found and the suggested records required for correct email delivery. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
reach_getProfileDomainDNSStatusV1 accepts 1 parameter: profileUuid. Required: profileUuid. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for reach_getProfileDomainDNSStatusV1: 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 Hostinger Api. Nothing to install.
reach_getProfileDomainDNSStatusV1 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 reach_getProfileDomainDNSStatusV1 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 reach_getProfileDomainDNSStatusV1. 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.
reach_getProfileDomainDNSStatusV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue