MCP server — What it can do (3)

• update_records — per-record skips with reasons; the result carries each record's previous values • trash_records — the restorable soft delete • restore_records — bring them back out again, which is what makes the line above true The write tools run the same checks as RowFold's own AI edits: field-level permissions, the posting seal, lifecycle rules, applied per record, with refusals skipped and the reason named rather than the batch failing. Every one takes a dry run that reports exactly what would happen and writes nothing. An update hands back each record's previous values, so posting those back is the undo. Trash is the restorable soft delete; nothing here destroys a record. Writes appear in the audit trail as MCP · connection (as person) and fire automations like any other save.