pages.set_custom_domain
Attach a custom hostname to a hosted static website. The hostname must be on a domain this Vee3 account already manages. Vee3 writes DNS and attaches the hostname to the page CDN with TLS. Subdomains use CNAME; the domain apex uses ALIAS. The preview hostname on vee3.site stays available. Setting...
This record as markdown: /tools/io-github-vee3io-vee3/pages.set-custom-domain.md
What pages.set_custom_domain does on Vee3
AI agents use pages.set_custom_domain to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
page_id | string | Yes | Page id to attach the custom domain to. |
custom_domain | string | Yes | Hostname to attach, such as www.example.com or example.com. Must be on a domain this Vee3 account already manages. At most 253 characters. |
Parameters from the server's own tool schema.
Why pages.set_custom_domain is rated Medium
Modifies DNS and CDN configuration; reversible by setting a new custom domain.
From the tool's definition Attach a custom hostname... replaces the previous one
Attacks that exploit this kind of access
The rule that runs pages.set_custom_domain 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 pages.set_custom_domain, this is the rule to start with:
pages.set_custom_domain stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 pages.set_custom_domain call is checked against it from then on.
Questions about pages.set_custom_domain
Attach a custom hostname to a hosted static website. The hostname must be on a domain this Vee3 account already manages. Vee3 writes DNS and attaches the hostname to the page CDN with TLS. Subdomains use CNAME; the domain apex uses ALIAS. The preview hostname on vee3.site stays available. Setting a new custom domain replaces the previous one. If HTTPS is not ready yet, call this tool again after DNS is live; Vee3 retries TLS issuance. Cost = 50 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
pages.set_custom_domain accepts 2 parameters: page_id, custom_domain. Required: page_id, custom_domain. 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 pages.set_custom_domain: 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.
pages.set_custom_domain is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pages.set_custom_domain 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 pages.set_custom_domain. 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.
pages.set_custom_domain 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