add_domain
Attach a custom domain to the site. Triggers DNS/ownership validation.
This record as markdown: /tools/webcake-storefront/add-domain.md
What add_domain does on Webcake Storefront
AI agents use add_domain to create or update resources in Webcake Storefront, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Webcake Storefront environment.
Why add_domain is rated Medium
Adding a domain is a write operation that modifies site configuration. While not destructive (it's reversible by removing the domain), it has high severity because: (1) it changes the public identity and routing of a storefront, potentially redirecting traffic or enabling phishing if abused; (2) it affects all customers accessing the site; (3) DNS/ownership validation suggests infrastructure-level impact.
From the tool's definition The tool description states 'Attach a custom domain to the site. Triggers DNS/ownership validation.' This is a persistent modification to site configuration that creates a new association between the storefront and a domain name.
Attacks that exploit this kind of access
The rule that runs add_domain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_domain, this is the rule to start with:
add_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 Webcake Storefront, apply this rule, and every add_domain call is checked against it from then on.
Questions about add_domain
Attach a custom domain to the site. Triggers DNS/ownership validation. It is categorised as a Write tool in the Webcake Storefront MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for add_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 Webcake Storefront. Nothing to install.
add_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 add_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 add_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.
add_domain is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Webcake Storefront, and thousands of servers like it.
This server
Across the catalogue