domains_getWHOISProfileUsageV1
Retrieve domain list where provided WHOIS contact profile is used. Use this endpoint to view which domains use specific contact profiles.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-getwhoisprofileusagev1.md
What domains_getWHOISProfileUsageV1 does on Hostinger Api
AI agents call domains_getWHOISProfileUsageV1 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 |
|---|---|---|---|
whoisId | integer | Yes | WHOIS ID |
Parameters from the server's own tool schema.
Why domains_getWHOISProfileUsageV1 is rated Low
This tool retrieves and queries existing data about WHOIS profile usage across domains. It performs a read-only lookup operation that returns information without modifying, deleting, executing code, or triggering financial transactions. The blast radius of misuse is minimal — an agent could only over-query or enumerate domains, not cause data loss or unauthorized state changes.
From the tool's definition Tool name contains 'get' and description explicitly states 'Retrieve domain list' and 'view which domains use specific contact profiles' — purely informational queries with no side effects.
Attacks that exploit this kind of access
The rule that runs domains_getWHOISProfileUsageV1 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 domains_getWHOISProfileUsageV1, this is the rule to start with:
domains_getWHOISProfileUsageV1 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 domains_getWHOISProfileUsageV1 call is checked against it from then on.
Questions about domains_getWHOISProfileUsageV1
Retrieve domain list where provided WHOIS contact profile is used. Use this endpoint to view which domains use specific contact profiles. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
domains_getWHOISProfileUsageV1 accepts 1 parameter: whoisId. Required: whoisId. 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 domains_getWHOISProfileUsageV1: 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.
domains_getWHOISProfileUsageV1 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_getWHOISProfileUsageV1 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_getWHOISProfileUsageV1. 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_getWHOISProfileUsageV1 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