delete_business_rule
Deletes a business rule after the person confirms; deprecating keeps it on the record instead.
Delete a business rule by business_rule_id. Its reference is never reused and the links to it go. The removal goes through the same action the Business Rules page runs and business_rule.deleted goes out. The tool is destructive: a Heimdall turn pauses for the person's confirmation and an MCP client asks before sending. Prefer moving a rule to deprecated with update_business_rule, so the record keeps what the business once decided. A staff token with business-rule:delete on the project is needed.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it.
Arguments
business_rule_id*stringUUID of the business rule to delete.
What it returns
{ "data": { "business_rule_id": "d4e5f6a7-b8c9-4d0e-9f1a-2b3c4d5e6f7a", "deleted": true }}How it fails
RESOURCE_NOT_FOUNDunknown business_rule_id, or a rule outside the token's scope or the person's visibility.
FORBIDDENthe token is a client guest's, or the holder's role on the project does not carry business-rule:delete.
TOKEN_MISSING_ABILITYtoken lacks business-rule:delete.
How is this guide?
Last updated on