pages.remove_custom_domain
Detach the custom hostname from a hosted static website. Removes the custom-domain DNS record and CDN hostname. The page stays online at the preview hostname on vee3.site. Cost = 5 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/pages.remove-custom-domain.md
What pages.remove_custom_domain does on Vee3
AI agents call pages.remove_custom_domain 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 |
|---|---|---|---|
page_id | string | Yes | Page id to detach the custom domain from. |
Parameters from the server's own tool schema.
Why pages.remove_custom_domain is rated Low
Even though pages.remove_custom_domain only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs pages.remove_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.remove_custom_domain, this is the rule to start with:
pages.remove_custom_domain 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 pages.remove_custom_domain call is checked against it from then on.
Questions about pages.remove_custom_domain
Detach the custom hostname from a hosted static website. Removes the custom-domain DNS record and CDN hostname. The page stays online at the preview hostname on vee3.site. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
pages.remove_custom_domain accepts 1 parameter: page_id. Required: page_id. 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.remove_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.remove_custom_domain 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 pages.remove_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.remove_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.remove_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