erase_customer

writes

One of the tools an AI assistant can call on an Avrosh account.

What it does

IRREVERSIBLY strip one person's identity from the records, GROUP-WIDE - every branch, every booking they are on (the business records survive, the person is scrubbed off them). This is the right-to-erasure verb for a request the business actually received. Before calling: read the person back to the human (get_customer), state that it is permanent and group-wide, and get an explicit yes. Then pass confirm: 'ERASE' - the tool refuses without it. There is no undo, and afterwards not even the audit trail can say who the row was about.

This is the exact text the model reads before deciding to call.

Parameters

business_idstringrequired

The id returned by list_businesses.

customer_idstringrequired

From list_customers.

confirmstringrequired

The literal string 'ERASE'. Only send it after the human explicitly confirmed.

one of: ERASE

Response

The result arrives as an MCP content block; the JSON in the panel is what the text field parses to.

Connecting

Point any MCP client at https://us.avrosh.com/mcp and log in — OAuth 2.1, no key to paste.

The panel here uses the other door: a bearer key made in the dashboard, for a script or a cron job with no browser to sign in with. Both reach the same endpoint. Full notes on the reference overview.

curl -X POST https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "erase_customer",
      "arguments": {
        "business_id": "926135ac-487d-4367-8bad-25397d0d4b87",
        "customer_id": "ct12…",
        "confirm": "ERASE"
      }
    }
  }'