Security & Privacy

Livy is designed to keep the agent approval boundary backend-owned while avoiding unnecessary custody of secrets.

Private Keys

Do not send private wallet keys to Livy.

The agent or wallet infrastructure signs locally. Livy evaluates policy, creates narrow approval state, verifies the exact action bundle, and records receipts.

Runtime API Keys

Runtime API keys are for server-side agent code.

Do not expose them in browsers, public repos, logs, prompts, or local skill files. The key should be scoped to the project and integration that the agent needs.

Dashboard Credentials

Agents should not receive dashboard admin credentials.

Use runtime keys for MCP. Keep admin access for human operators and backend administration.

Evidence And Receipts

Livy records action state so operators can inspect what happened:

• request payload metadata
• wallet profile match
• guardrail decision
• policy hash or version
• approval nonce and expiry
• execution status
• receipt state

Private source material should be committed by reference or hash when possible. Do not make raw private artifacts public unless your product policy requires it.

Direct Sends

Direct wallet sends bypass Livy policy and receipt tracking.

If an action must be governed by Livy, route it through MCP.