Supabase Set Secret
supabase_set_secretSets one edge-function secret on a Supabase project server-side, ideal for adding a single value like FAL_KEY; live writes require human approval and values are never echoed.
Instructions
Write one edge-function secret on a Supabase project, server-side only (live write, needs human approval).
Use when: adding a single secret such as FAL_KEY. backend_deploy sets the standard set for you. Returns: {ok, name} (value never echoed), or an approval_required refusal.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"ref": "<ref>",
"name": "<name>",
"value": "<value>"
},
"name": "supabase_set_secret"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ref | Yes | Supabase project ref (20-char id from supabase_list_projects, e.g. 'abcdefghijklmnopqrst'). | |
| name | Yes | Edge function secret name, e.g. 'FAL_KEY'. | |
| value | Yes | Secret value; written server-side and never echoed back. | |
| approval_id | No | Approval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||