This record as markdown: /tools/hostinger-mcp/domains-get-whois-profile.md
What domains_get_whois_profile does on Hostinger
AI agents call domains_get_whois_profile 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.
Why domains_get_whois_profile is rated Low
This tool queries and returns WHOIS profile information for a domain. WHOIS data is public registration information. The operation is read-only with no side effects, making it a Read category tool. Severity is low because WHOIS data is publicly available and non-sensitive in nature.
From the tool's definition 'Get a specific WHOIS profile' — retrieves WHOIS data about a domain; no modification or side effects.
Attacks that exploit this kind of access
The rule that runs domains_get_whois_profile 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 domains_get_whois_profile, this is the rule to start with:
domains_get_whois_profile 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, apply this rule, and every domains_get_whois_profile call is checked against it from then on.
Questions about domains_get_whois_profile
Get a specific WHOIS profile. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for domains_get_whois_profile: 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.
domains_get_whois_profile 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 domains_get_whois_profile 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 domains_get_whois_profile. 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.
domains_get_whois_profile 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.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue