New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

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

Questions about pages.remove_custom_domain

What does the pages.remove_custom_domain tool do? +

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.

What parameters does pages.remove_custom_domain accept? +

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.

How do I enforce a policy on pages.remove_custom_domain? +

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.

What risk level is pages.remove_custom_domain? +

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

Can I rate-limit pages.remove_custom_domain? +

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.

How do I block pages.remove_custom_domain completely? +

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.

What MCP server provides pages.remove_custom_domain? +

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.

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 Vee3'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.