set_custom_domain
Configure a custom domain for your public-facing pages (e.g., clients.mybusiness.com). The client adds a CNAME record pointing to cname.businys.app.
This record as markdown: /tools/app-businys-mcp-server/set-custom-domain.md
What set_custom_domain does on Businys
AI agents use set_custom_domain to create or update resources in Businys, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Businys environment.
Why set_custom_domain is rated Medium
This tool creates or modifies domain configuration settings, which is a reversible change that affects the public accessibility and routing of the service. While it does not delete data or execute arbitrary code, it makes persistent changes to infrastructure settings (DNS/domain configuration). This qualifies as Write rather than Execute because the effect is configuration modification, not code execution.
From the tool's definition Tool description explicitly states 'Configure a custom domain for your public-facing pages' and involves adding CNAME records, which modifies DNS configuration and domain routing settings that affect how the service is accessed.
Attacks that exploit this kind of access
The rule that runs set_custom_domain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_custom_domain, this is the rule to start with:
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 Businys, apply this rule, and every set_custom_domain call is checked against it from then on.
Questions about set_custom_domain
Configure a custom domain for your public-facing pages (e.g., clients.mybusiness.com). The client adds a CNAME record pointing to cname.businys.app. It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Businys MCP server in PolicyLayer and add a rule for 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 Businys. Nothing to install.
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 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 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.
set_custom_domain is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue