domains.check_availability
Check whether domain names can be registered through Vee3 (Namecheap-backed). Returns a map of each requested domain name to a boolean: true when the domain is available for purchase through Vee3, false when it is not. Cost = 5 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/domains.check-availability.md
What domains.check_availability does on Vee3
AI agents call domains.check_availability to retrieve information from Vee3 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 |
|---|---|---|---|
domains | array | Yes | Domain names to check (maximum 10). |
Parameters from the server's own tool schema.
Why domains.check_availability is rated Low
Tool queries domain availability without modifying, purchasing, or executing operations.
From the tool's definition Check whether domain names can be registered; returns boolean availability status.
Attacks that exploit this kind of access
The rule that runs domains.check_availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domains.check_availability, this is the rule to start with:
domains.check_availability 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 Vee3, apply this rule, and every domains.check_availability call is checked against it from then on.
Questions about domains.check_availability
Check whether domain names can be registered through Vee3 (Namecheap-backed). Returns a map of each requested domain name to a boolean: true when the domain is available for purchase through Vee3, false when it is not. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
domains.check_availability accepts 1 parameter: domains. Required: domains. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for domains.check_availability: 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 Vee3. Nothing to install.
domains.check_availability 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.check_availability 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.check_availability. 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.check_availability is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue