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

bind_domain

Bind one or more of YOUR tracked domains to sites in a project (Cloudflare zone + registrar nameserver flip, then background completion — the domain typically goes live within minutes once NS propagates; poll list_domains for binding → bound). Pass pairs as an array of { domain, siteId } (max 20;...

SERVERA3plus SOURCEa3plus-mcp
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a3plus-mcp/bind-domain.md

What bind_domain does on A3plus

AI agents call bind_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.

ParameterTypeRequiredDescription
pairs array Yes Domain → site pairings, each { domain, siteId }. Max 20 per call.
projectId string Yes The TARGET project ID — the project containing the sites to bind onto.

Parameters from the server's own tool schema.

Why bind_domain is rated Low

Even though bind_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 bind_domain

What does the bind_domain tool do? +

Bind one or more of YOUR tracked domains to sites in a project (Cloudflare zone + registrar nameserver flip, then background completion — the domain typically goes live within minutes once NS propagates; poll list_domains for binding → bound). Pass pairs as an array of { domain, siteId } (max 20; a single bind is a one-element array). Each domain must be available (unbind_domain it first if bound) and each target site must not already have a verified domain. CROSS-PROJECT MOVES: projectId is the TARGET project; a domain currently inventoried in another of your projects is transferred automatically — that path requires a Personal Access Token (ak_user_) with owner access to BOTH projects. Only domains already tracked in your own projects can be bound — this tool cannot claim domains from the shared registrar pool (use the dashboard for that). Banned/blocked domains (see list_domains blockedDomains) are always refused. Per-pair failures are isolated and reported; a failed pair auto-releases its domain back to available. It is categorised as a Read tool in the A3plus MCP Server, which means it retrieves data without modifying state.

What parameters does bind_domain accept? +

bind_domain accepts 2 parameters: pairs, projectId. Required: pairs, projectId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bind_domain? +

Register the A3plus MCP server in PolicyLayer and add a rule for bind_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.

What risk level is bind_domain? +

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

Can I rate-limit bind_domain? +

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

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

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

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