Guardrails, secrets and version history
Set hard limits on an agent, store keys safely for its web calls, and restore an earlier version.
Three sections on an agent's page protect you after you have built it.
Guardrails
Hard limits that the agent cannot talk its way past. On the Edit tab, the Guardrails section has four settings. Leave a field empty for no limit, and choose Save changes to apply.
- Daily spend limit (USD).
- Runs per day.
- Allowed web domains, one per line. When set, web calls go only to these domains and their subdomains.
- Ask me first when an amount is over: any tool call with an argument named
amount,totalorvalueabove this number asks for your approval.
Secrets
The Secrets section stores keys and tokens that an agent's web calls and connected servers need. Values are write-only.
- Enter a Name in capital letters, numbers and underscores, such as
SERVICE_API_KEY, and the Value. - Optionally set Only send to these domains (optional).
- Choose Add secret. Only the name and last four characters show afterwards. Replace secret swaps the value and Remove deletes it.
- Write
{{secret:NAME}}in a web call's address, headers or body. It is filled in only when the call is made, so the agent and the run history never see the value.
If a secret an agent needs is missing, a banner names it.
Version history
On the Versions tab, every save that changes instructions, tools, schedule, model, approvals, budgets or guardrails is kept. Each entry lists what changed, and runs show the version they used.
Choose Restore this version and confirm to go back. The old settings are saved as a new version, so nothing is lost.
Good to know
- Keep secrets out of instructions, memory and run inputs.
- Test the effect of a change before you save it. See Test and replay an agent.
- For where else keys live, see Choose tools and understand which need approval.
More guides in PGB Agents
What a PGB Agent is and what it can do
An agent is a saved job with instructions, a list of allowed tools, a budget and a record of every step it takes.
Create an agent from scratch or from the Marketplace
Make a blank agent in two clicks, or add a ready-made one from PGB Marketplace and review it before it runs.
Write good instructions for an agent
How to word the Instructions box so an agent does the right job, stays inside its limits and tells you when it is unsure.
Choose tools and understand which need approval
The list of tools an agent can use, what each does, and which ones always pause for your approval.
Start agents manually, on a schedule or from a webhook
Run an agent by hand, set it to repeat with the schedule builder, or give it a private web address that starts a run.
Set budgets and know when a run will stop
Put a dollar limit on each run and each month, and learn the other limits that stop an agent from running away.