Agent Wallet
The public wallet profile Livy uses to match MCP requests to protected actions.
An agent wallet is the public configuration Livy uses to recognize which wallet, asset, network, and action type a request is trying to use.
It is not a private key vault. Livy never needs the agent's private key to evaluate policy.
What It Contains
A wallet profile usually includes:
- wallet id
- display name
- network
- public key
- source vault or public wallet reference
- asset or mint
- protected action type
- status
The dashboard shows active profiles under Wallet Config.
Why It Exists
Guardrails need a stable target.
When an MCP request arrives, Livy checks whether the request matches a known wallet profile. That match lets Livy choose the right guardrail and reject requests that are trying to use a different wallet, asset, network, or action type.
Matching Rules
Treat the wallet profile as the identity layer for protected actions:
- The public key must match the wallet the agent is using.
- The network must match the execution environment.
- The asset or mint must match the protected action.
- The action type must match the action the agent is requesting.
- Archived or inactive profiles should not authorize new requests.
If a request cannot be matched to an active profile, it should not receive approval.
Private Keys
Do not paste a private key into Livy.
The agent or wallet infrastructure signs locally. Livy evaluates policy and authorizes one exact action bundle. That separation keeps the approval boundary backend-owned without turning Livy into a general wallet custodian.