Call site.database.execute

Change what a site's own database holds — 'add that product to my site's shop', 'update the price in the site's database', 'delete that stale record from the site'. Change this site's own database with one SQL statement — insert, update, delete, or a schema change the site's code expects. Calling it raises the approval card showing the exact statement — and, for an update or delete, how many rows it touches — which is the member's confirmation. Put every value in params as a ? placeholder, and read the schema with site.database.query before writing. NEVER run a delete or update without a where clause, and never describe anything as changed before the member has approved. Not for reading the database — that is site.database.query. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.