Administer
Secret requests
On this page
What a request is
No tool on Valet's MCP server takes a secret. When your
agent needs an API key, a visitor password, or a sign-in with another
service, the tool it calls returns a link instead. The link opens a
request page in your dashboard, at /<org>/requests/<id>. You
enter the value there, or sign in to the service from there, and Valet
applies it.
The value goes from your browser to Valet. It never passes through the conversation, and your agent never sees it. Your agent learns only whether you finished, and the names of what was set.
Ask your agent:
Add my Stripe key to shop as STRIPE_KEY.set_env_vars
{
"name": "shop",
"secret_names": ["STRIPE_KEY"],
"reason": "The shop needs your Stripe key to take payments."
}
get_request
{ "id": "<request id>", "wait_seconds": 20 }Your agent gives you the link, then waits with get_request until you
finish, decline, or the link expires.
What asks for one
set_env_vars
- The page asks for
- Secret env vars on an app or agent
attach_resource
- The page asks for
- Secret env vars set beside a resource
create_connector
- The page asks for
- A connector's API keys, or a sign-in with its service
reauthorize_connector
- The page asks for
- A new sign-in with a connector's service
set_service_access
- The page asks for
- The visitor password, for password access
set_policy
- The page asks for
- A release policy checker's secret settings
In a dedicated installation, attach_resource and set_resource_plan
also open a request when the resource is a
private system. That request asks an
Admin to approve access, takes no value, and lasts 24 hours.
Each request carries a reason your agent wrote, so you can see why it asked. The page also shows what the request changes, such as the artifact, app, or agent it is for, who asked, and when it expires.
Who can complete it
The link is not a credential. Any member of the organization can open it after signing in to Valet. Completing it needs the permission the action itself needs: the Developer role to set an app's or agent's secrets, add a connector, or set a visitor password, and the Admin role for a release policy's secrets, in an organization that enforces roles. A member without that permission sees who can complete it, and can send the link to that person.
You can also decline a request. Declining applies nothing, and your agent is told.
Find your requests
Open Governance, then Access requests, in the dashboard. The page lists every request you can see, of every kind:
- Needs your attention lists the open requests you can act on now: the ones your role can complete, and the ones your agent opened. Each shows what it asks for, who asked, and when it expires. Enter or Sign in opens the request page. An Admin approves or declines a private-system request from the list. A badge on Governance counts these requests.
- History lists the requests that were completed, declined, or expired, newest first. Each shows who completed or declined it, when, and the decliner's note. It never shows a value.
You see the requests you opened, the requests on an app, site, or agent you can see, and the requests your role can complete. An Admin sees every request in the organization. A row opens the request's page.
How long it lasts
A request expires 15 minutes after your agent makes it. Once a request is completed, declined, or expired, the link applies nothing more. Ask your agent to try again for a new link.
A request for a sign-in finishes when the service sends you back to the page. The page then shows the connector as connected.
If you paste a secret into the conversation
Don't. If you do, enter the value on the request page instead, and rotate the secret at the service it came from, since it is now in the conversation's history. No tool accepts it, so pasting it does not set it.
From the CLI
The CLI still takes secrets directly, from your own terminal:
valet env set NAME=VALUEtakes the value as an argument.valet sites access <name> passwordandvalet apps access <name> passwordprompt for the password without showing it, or take--passwordin a script.valet policies addprompts for a checker's missing secret setting, or reads it from a file with--set key=@file.
Run these yourself rather than asking an agent to, so the value stays in your terminal.
Next steps
- Data access: env vars and how apps and agents read them.
- Connectors: add a connector and sign in to its service.
- MCP server: the tools that make requests.