Use stored secrets
Approve a bounded API call without putting a credential into your agent’s conversation.
guide~3 minVerified v0.237.0
Goal
Let an agent call a service using a credential it cannot read.
What you'll have
An encrypted secret field and an owner-approved grant: permission for one agent to use that field on one host, within a time and use limit.
Needs
A content collection entry with a text field classified pii: secret, a connected agent with secret-use permission, and the workspace owner to enter the value and approve its use. Visitor submissions cannot be used this way.
Prompt
Steps
- Ask your agent to define the collection with
super_data_schema. Open its entry under Data → Collections and type the credential yourself. Entry reads show whether it is set, without returning its value. - Ask the agent to call
super_secret_use, naming the collection, entry, field, method and public HTTPS URL. It proposes one header, such asauthorizationwith prefixBearer. - The first call returns
approval_requiredand an approval link. Open it as the workspace owner. Check the agent, field, exact host, method and header. Approve only the access needed: defaults are 24 hours and 50 uses; maximums are 30 days and 1,000 uses. - Have the agent repeat the call after approval. The platform decrypts the value, adds it to the approved header and calls that host. Redirects are not followed.
Check it worked
The agent gets status, headers and a scrubbed response, never the credential. Open Secret use to inspect or revoke the grant. Grant decisions and uses are recorded in the workspace audit log; access to that log follows your plan.
If not
secret_echoed means the service reflected the secret and the whole response was withheld. Do not ask the agent to bypass this. host_not_allowed or method_not_allowed means the call exceeds the grant. After expiry or exhaustion, a new approval is needed. A denial or revocation stands for a day.
Variations
Only the workspace owner can reveal a stored value in the dashboard. For software that needs a local credential, enter it yourself there. Secret use sends credentials in a header, never in the URL or body.
Next
Read security boundaries and limits, MCP tools and plans.