v2_getDomainVerificationsDIRECT

Retrieve a list of pending and completed domain verifications.

SERVERHostinger Api SOURCEhostinger-api-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/io-github-hostinger-hostinger-api-mcp/v2-getdomainverificationsdirect.md

What v2_getDomainVerificationsDIRECT does on Hostinger Api

AI agents call v2_getDomainVerificationsDIRECT 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.

Why v2_getDomainVerificationsDIRECT is rated Low

This tool retrieves domain verification status information without any side effects, reversible writes, destructive actions, financial operations, or code execution. It is a straightforward data retrieval operation, making it a Read category risk with low severity since domain verification data exposure has limited blast radius.

From the tool's definition Tool name contains 'get' and description states 'Retrieve a list of pending and completed domain verifications' — a read-only query operation with no data modification, deletion, or execution of external commands.

Questions about v2_getDomainVerificationsDIRECT

What does the v2_getDomainVerificationsDIRECT tool do? +

Retrieve a list of pending and completed domain verifications. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on v2_getDomainVerificationsDIRECT? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for v2_getDomainVerificationsDIRECT: 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.

What risk level is v2_getDomainVerificationsDIRECT? +

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

Can I rate-limit v2_getDomainVerificationsDIRECT? +

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

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

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

Across the catalogue

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