unbind_domain
Release a custom domain from the site it is currently bound to. The site keeps serving on its a3plus test domain; the released domain returns to the SAME project's inventory as available, ready for bind_domain. This is step 1 of moving a domain to another site or project (step 2 = bind_domain on ...
This record as markdown: /tools/a3plus-mcp/unbind-domain.md
What unbind_domain does on A3plus
AI agents call unbind_domain to retrieve information from A3plus 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 |
|---|---|---|---|
domain | string | Yes | The domain to release, e.g. "example.com". |
projectId | string | Yes | The project that currently owns the domain (see list_domains). |
Parameters from the server's own tool schema.
Why unbind_domain is rated Low
Even though unbind_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 unbind_domain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unbind_domain, this is the rule to start with:
unbind_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 A3plus, apply this rule, and every unbind_domain call is checked against it from then on.
Questions about unbind_domain
Release a custom domain from the site it is currently bound to. The site keeps serving on its a3plus test domain; the released domain returns to the SAME project's inventory as available, ready for bind_domain. This is step 1 of moving a domain to another site or project (step 2 = bind_domain on the target project). The live site stops resolving on this domain IMMEDIATELY — confirm with the user before calling. Requires owner access to the project (editors cannot unbind). It is categorised as a Read tool in the A3plus MCP Server, which means it retrieves data without modifying state.
unbind_domain accepts 2 parameters: domain, projectId. Required: domain, projectId. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for unbind_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 A3plus. Nothing to install.
unbind_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 unbind_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 unbind_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.
unbind_domain is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A3plus, and thousands of servers like it.
This server
Across the catalogue