domain_bindings_delete
Run domain-bindings.delete through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/domain-bindings-delete.md
What domain_bindings_delete does on Appaloft
AI agents call domain_bindings_delete to permanently remove resources in Appaloft, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirmation | object | Yes | |
idempotencyKey | string | — | |
domainBindingId | string | Yes |
Parameters from the server's own tool schema.
Why domain_bindings_delete is rated Critical
An AI agent that decides to call domain_bindings_delete doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Appaloft is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs domain_bindings_delete 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_delete, this is the rule to start with:
domain_bindings_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every domain_bindings_delete call is checked against it from then on.
Questions about domain_bindings_delete
Run domain-bindings.delete through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
domain_bindings_delete accepts 3 parameters: confirmation, idempotencyKey, domainBindingId. Required: confirmation, domainBindingId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for domain_bindings_delete: 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.
domain_bindings_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the domain_bindings_delete 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 domain_bindings_delete. 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.
domain_bindings_delete 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.
More on Appaloft, and thousands of servers like it.
Across the catalogue