sitebay_add_custom_hostname

Attach a custom domain (e.g. shop.theirclient.com) to a site via Cloudflare for SaaS

Server SiteBay MCP Server sitebay/sitebay-mcp
Category Write
Risk class Medium
Parameters 00 required

What sitebay_add_custom_hostname does on SiteBay MCP Server

AI agents use sitebay_add_custom_hostname to create or update resources in SiteBay MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SiteBay MCP Server environment.

Why sitebay_add_custom_hostname needs a policy

This tool modifies site configuration by attaching a custom domain, which is a Write-category action (creates or modifies data reversibly). The severity is high because misconfiguration could redirect legitimate traffic to wrong destinations or enable phishing attacks if an AI agent adds a malicious domain. The action is reversible (domains can be detached), so it does not qualify as Destructive.

From the tool's definition The tool 'sitebay_add_custom_hostname' is described as 'Attach a custom domain...to a site via Cloudflare for SaaS', which performs a reversible configuration change that creates/modifies DNS or domain routing settings.

Questions about sitebay_add_custom_hostname

What does the sitebay_add_custom_hostname tool do? +

Attach a custom domain (e.g. shop.theirclient.com) to a site via Cloudflare for SaaS. It is categorised as a Write tool in the SiteBay MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sitebay_add_custom_hostname? +

Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_add_custom_hostname: 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 SiteBay MCP Server. Nothing to install.

What risk level is sitebay_add_custom_hostname? +

sitebay_add_custom_hostname is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sitebay_add_custom_hostname? +

Yes. Add a rate_limit block to the sitebay_add_custom_hostname 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 sitebay_add_custom_hostname completely? +

Set action: deny in the PolicyLayer policy for sitebay_add_custom_hostname. 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 sitebay_add_custom_hostname? +

sitebay_add_custom_hostname is provided by the SiteBay MCP Server MCP server (sitebay/sitebay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.