list_secrets - kubed-io/selenium-flow GitHub Wiki
The secrets this caller may bind.
| MCP resource | secret://secrets |
| HTTP | GET /secrets |
The secrets you can bind to a field, by name.
You never see a value — not here, not anywhere. Each entry gives the secret's name, the keys inside it, what it is for, and the sites it may be used on.
To use one, do NOT ask for it: name it where the value would go. Pass write a secret instead of text — secret={'name': ..., 'key': ...} — or in a saved flow put the same thing in that step's args. The server reads it and types it; it never passes through you, which is the point.
A secret listing allowed_urls may only be used on those sites. One that is not restricted may be used anywhere. If an entry carries allowed_urls_rejected, its leash is broken and it cannot be used at all until an operator fixes the file.
This action takes no parameters.
Every call names its workspace: an X-Workspace header, or
?workspace=<name>. Sending both is refused. See Workspaces.
| Field | Type | Notes |
|---|---|---|
count |
integer | |
workspace |
string | |
secrets |
array |
| Status | Means |
|---|---|
400 |
No workspace named, two names given, or a server started with no secrets.dirs and no secrets.entries, so there are no secrets to list. |
401 |
Missing or wrong bearer token. |
500 |
Something failed that this server did not expect. |
Over MCP the same failures arrive as a tool error.
MCP
read secret://secrets
read_resource(uri="secret://secrets")
HTTP
curl -X GET $SELENIUM_FLOW/secrets \
-H "Authorization: Bearer $TOKEN" \
-H "X-Workspace: $WORKSPACE"