Policy
Set an agent's policy in the Thirdfy dashboard. Approvals, kill switch, spending limits, risk limits, allowed actions, and signing the wallet policy.
Each agent has a policy: what it may do, how much it may spend, and when a write waits for you. Thirdfy checks every write against it before a wallet signs. If it does not clear, it does not execute.
Open it from the agent's page with Policy, at thirdfy.com/my-agents/<agentKey>/policy.
Reads always work. The policy governs writes: trades, deposits, orders, transfers and venue setup.
Approvals
Approvals decide when a write waits for you before it runs.
| Mode | What happens |
|---|---|
| Always ask | Every write waits for your approval. The default |
| Ask above an amount | Writes at or under the amount you set run without asking. Larger ones wait |
| Never ask | Writes run as soon as they clear the policy. For hosted agents |
Choose a mode and click Save. Never ask asks you to confirm first. The allowed actions, limits and venue checks still apply in every mode.
Kill switch
Pause now refuses every write by this agent at once, before it signs. Reads keep working. You can add a reason. Nothing already signed is undone.
While the agent is paused, the card shows when and why. Resume lets writes run again when they clear the policy.
You pause from the app without touching the agent's host. Revoking the agent's key on Connect also pauses it, and a new key does not resume it. Resume here.
Limits
Two caps, in USD, checked before any write signs:
| Limit | What it caps |
|---|---|
| Per action (USD) | The most a single write may commit. Empty means no cap |
| Per day (USD) | The total the agent's writes may commit in a day |
The per-action cap can't be above the daily cap. Click Save limits.
Without limits, a write can spend up to what the wallet holds. The agent's Setup card reminds you until you set one.
Risk
Risk limits are checked before a new position opens. An empty field is not checked.
| Field | What it limits |
|---|---|
| Max leverage | Leverage on a new position |
| Max loss at stop (% of equity) | The loss a new position may take at its stop |
| Max open positions | How many positions may be open at once |
| Max new entries per day (UTC) | How many positions the agent may open in a day |
| Require a stop-loss on every new entry | A new position must carry a stop-loss |
Click Save risk limits.
Allowed actions
The agent can only run what is switched on here. Everything else is refused before a wallet signs.
Actions are grouped by protocol, with a count such as "3 of 12 allowed". Search by action or protocol name, then switch each action on or off.
You can also allow a protocol's actions from its page in Protocols.
Wallet policy
Some agents run on a wallet you own (an owner-controlled agent wallet). That wallet has its own policy, and Thirdfy's signer can only do what it allows. A new partner protocol works on that wallet only after you sign it into the wallet policy.
You'll be sent here when:
- you switch on a partner protocol's action and the app says Wallet policy update needed;
- a venue says the owner must sign a wallet policy update;
- a write in Command is refused with Owner signature needed.
Open Wallet policy on the agent's page, at thirdfy.com/my-agents/<agentKey>/wallet-policy.
- Read what the policy allows: the protocols and venues, each function the wallet may call and on which contracts, the token spenders it may approve, and how much of the chain's native coin each call may send.
- Click Sign and submit. You sign with your own key in the browser. Thirdfy relays your signature and adds none of its own.
- When it shows Policy updated, run the refused action again.
The request is valid for a few minutes. If it expires, click Build the request again, then sign.
If the agent's wallet is not owner-controlled, the page says No user-owned wallet: there is no wallet policy for you to sign, and partner protocols can't run on it.
What happens on each write
- Your agent asks for an action, from your client, the CLI or Command.
- Thirdfy checks it: the agent is owned, active and not paused, the action is allowed, it fits the limits and risk, the venue is ready, and Credits can pay.
- If your approval mode asks, the write waits for you.
- The wallet signs, and the action shows in Activity with its receipt.
A write that fails a check is refused before anything is signed. It still shows in Activity, as Blocked, with the reason.
Related
- Agents: Setup checklist and venues
- Activity: Cleared and blocked actions
- The wallet rule: Why partner writes need an owner-controlled wallet
- Delegation and protection: Deeper technical reference for builders