domains_get_whois_profile_usage

Get domains using 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-usage.md

WHAT IT DOES

What domains_get_whois_profile_usage does on Hostinger

AI agents call domains_get_whois_profile_usage 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 domains_get_whois_profile_usage is rated Low

This tool queries and retrieves information about which domains are associated with a WHOIS profile. It performs a read-only lookup with no ability to modify, delete, or execute actions. The blast radius of misuse is minimal — an agent could view domains linked to a profile but cannot alter them.

From the tool's definition Tool name includes 'get' and description states 'Get domains using a specific WHOIS profile' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs domains_get_whois_profile_usage 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_usage, this is the rule to start with:

domains_get_whois_profile_usage Allowed

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

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 domains_get_whois_profile_usage call is checked against it from then on.

FAQ

Questions about domains_get_whois_profile_usage

What does the domains_get_whois_profile_usage tool do? +

Get domains using 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_usage? +

Register the Hostinger MCP server in PolicyLayer and add a rule for domains_get_whois_profile_usage: 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_usage? +

domains_get_whois_profile_usage 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_usage? +

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

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

domains_get_whois_profile_usage 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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