New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

domains_get_whois_profile

Get a specific WHOIS profile.

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/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.

Questions about domains_get_whois_profile

What does the domains_get_whois_profile tool do? +

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.

How do I enforce a policy on domains_get_whois_profile? +

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.

What risk level is domains_get_whois_profile? +

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

Can I rate-limit domains_get_whois_profile? +

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.

How do I block domains_get_whois_profile completely? +

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.

What MCP server provides domains_get_whois_profile? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.