domains.register
Register a domain through Vee3. The user or agent passes registrant contact details and expected_token_cost from domains.registration_quote. Use a real registrant email address the domain owner can access; the registrar may send a verification email that must be completed to keep the domain in go...
This record as markdown: /tools/io-github-vee3io-vee3/domains.register.md
What domains.register does on Vee3
AI agents use domains.register to commit financial operations through Vee3, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
years | integer | — | Registration term in years. |
domain | string | Yes | Domain name to register (for example example.com). |
contact | object | Yes | Registrant contact used for Registrant, Admin, Tech, and AuxBilling roles. Object with first_name, last_name, address1, city, state_province, postal_code, count |
enable_privacy | boolean | — | Whether to enable free WhoisGuard privacy protection when available. |
expected_token_cost | integer | Yes | Token cost from a fresh domains.registration_quote response. Required to prevent surprise charges. |
Parameters from the server's own tool schema.
Why domains.register is rated Critical
Registers a domain and charges tokens, committing a financial obligation on success.
From the tool's definition Charges the quoted token cost on success
Attacks that exploit this kind of access
The rule that runs domains.register 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.register, this is the rule to start with:
Any call to domains.register is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every domains.register call is checked against it from then on.
Questions about domains.register
Register a domain through Vee3. The user or agent passes registrant contact details and expected_token_cost from domains.registration_quote. Use a real registrant email address the domain owner can access; the registrar may send a verification email that must be completed to keep the domain in good standing. Charges the quoted token cost on success. Cost = 200 tokens + domain registration price in tokens. It is categorised as a Financial tool in the Vee3 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
domains.register accepts 5 parameters: years, domain, contact, enable_privacy, expected_token_cost. Required: domain, contact, expected_token_cost. 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.register: 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.register is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the domains.register 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.register. 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.register 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.
Across the catalogue