Harness docs
Quickstart
Install harness-mcp, create a limits.yaml, and add Harness to your agent's MCP configuration with your wallet address. The agent now requests signatures through Harness instead of directly.
Start with a low per_day cap such as 1 SOL, run the agent for a day, then read the log to see which actions were blocked and why before loosening anything.
Limits file reference
per_trade and per_day are amounts in SOL or USDC. assets lists token symbols or mint addresses, and venues lists allowed programs such as jupiter or orca. max_slippage_bps is the highest slippage Harness will approve, measured on the simulated route.
Set require_reason to true and Harness blocks any request that arrives without a stated reason, so every log entry explains itself.
Verifying the log
Each entry contains the previous entry's signature, so the log forms a chain. The public log page shows a check mark when the whole chain verifies, and flags the first broken entry if it does not.
Approved entries link to the transaction on Solscan so viewers can confirm the on-chain result matches what the log says.