reach_profiles_dns_status

Check DNS configuration status for a profile domain.

SERVERHostinger SOURCEidugeni/hostinger-mcp

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/hostinger-mcp/reach-profiles-dns-status.md

WHAT IT DOES

What reach_profiles_dns_status does on Hostinger

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

RISK

Why reach_profiles_dns_status is rated Low

This tool performs a status check on DNS configuration, which is a read-only operation that retrieves information about an existing domain's DNS setup. It has no side effects, does not modify data, and does not execute arbitrary commands. The 'check' and 'status' terminology confirms it is a diagnostic/informational query rather than a configuration change.

From the tool's definition Tool name 'reach_profiles_dns_status' and description 'Check DNS configuration status for a profile domain' indicate a query/inspection operation that retrieves DNS configuration information without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reach_profiles_dns_status safely

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

reach_profiles_dns_status Allowed

reach_profiles_dns_status 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": {
    "reach_profiles_dns_status": {}
  }
}

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

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

FAQ

Questions about reach_profiles_dns_status

What does the reach_profiles_dns_status tool do? +

Check DNS configuration status for a profile domain. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on reach_profiles_dns_status? +

Register the Hostinger MCP server in PolicyLayer and add a rule for reach_profiles_dns_status: 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. Nothing to install.

What risk level is reach_profiles_dns_status? +

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

Can I rate-limit reach_profiles_dns_status? +

Yes. Add a rate_limit block to the reach_profiles_dns_status 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 reach_profiles_dns_status completely? +

Set action: deny in the PolicyLayer policy for reach_profiles_dns_status. 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 reach_profiles_dns_status? +

reach_profiles_dns_status is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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