MCP tools: remote-secret-requests
remote-secret-requests
Registered when: platform: vault.requests + org: vaultRequests.enabled (both on by default).
read_requested_secret
Read the value a member stored for one of YOUR secret requests (request_secret). Only the principal that asked can read it; every read is logged. If the request is still pending this returns its status instead. Use the value for the task it was requested for; never echo it into chat, tickets, commits or logs.
| Parameter | Type | Required | Description |
|---|---|---|---|
requestId | string | yes | The id request_secret returned. |
Example call:
{"name":"read_requested_secret","arguments":{"requestId":"<requestId>"}}
Related: request_secret.
request_secret
Ask an org member for a password, API key or token. They enter it in a secure, masked form in GoodQA; it is stored encrypted in the vault and only you (this principal) can read it, with read_requested_secret. Never ask anyone to paste a secret into chat, and never put a secret in the reason. Pass conversationId (e.g. your DM with them) to post the request as a secure-form card. Returns the request id and status.
| Parameter | Type | Required | Description |
|---|---|---|---|
requestedFromUserId | string | yes | The member to ask (uuid). |
name | string | yes | What you need, e.g. "Stripe live secret key". Becomes the vault secret name. |
kind | "password" \ | "api_key" \ | "token" \ |
reason | string | yes | Why you need it (shown to them before they type anything). Never include a secret. |
projectId | string | no | Store at this project scope instead of org scope. |
conversationId | string | no | Post the request into this conversation as a secure-form card. |
expiresInDays | integer | no | 1-30, default 7. |
Example call:
{"name":"request_secret","arguments":{"requestedFromUserId":"<requestedFromUserId>","name":"<name>","reason":"<reason>"}}
Related: read_requested_secret.