domain_bindings_create

Run domain-bindings.create through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp

Medium RISK CLASS

Category Write

Parameters 125 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/domain-bindings-create.md

WHAT IT DOES

What domain_bindings_create does on Appaloft

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

Parameter	Type	Required
`tlsMode`	string	—
`serverId`	string	—
`projectId`	string	Yes
`proxyKind`	string	Yes
`domainName`	string	Yes
`pathPrefix`	string	—
`redirectTo`	string	—
`resourceId`	string	Yes
`pathHandling`	string	—
`destinationId`	string	—
`environmentId`	string	Yes
`idempotencyKey`	string	—

Parameters from the server's own tool schema.

RISK

Why domain_bindings_create is rated Medium

This tool creates new domain binding records, modifying application configuration. This is a Write operation—it creates/modifies data reversibly without deleting data or executing arbitrary code. Severity is medium because misconfigured domain bindings could disrupt service routing or DNS resolution, but the blast radius is limited to domain binding scope and effects are reversible.

From the tool's definition Tool name 'domain_bindings_create' and description indicating it 'create[s]' domain bindings through an application operation catalog. The action is reversible (bindings can be updated or deleted) but affects system configuration.

Risk signalsHigh parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs domain_bindings_create safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domain_bindings_create, this is the rule to start with:

domain_bindings_create Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "domain_bindings_create": {
      "limits": [
        {
          "counter": "domain_bindings_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every domain_bindings_create call is checked against it from then on.

FAQ

Questions about domain_bindings_create

What does the domain_bindings_create tool do? +

Run domain-bindings.create through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does domain_bindings_create accept? +

domain_bindings_create accepts 12 parameters: tlsMode, serverId, projectId, proxyKind, domainName, pathPrefix, redirectTo, resourceId, pathHandling, destinationId, environmentId, idempotencyKey. Required: projectId, proxyKind, domainName, resourceId, environmentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on domain_bindings_create? +

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

What risk level is domain_bindings_create? +

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

Can I rate-limit domain_bindings_create? +

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

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

domain_bindings_create is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 358 Appaloft tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →