PocketAgent

Security

Encryption, spending caps, write-tool gates, and production hardening.

Key material

  • Agent private keys are AES-256 encrypted with ENCRYPTION_KEY before SQLite storage.
  • Access tokens are stored as hashes only — plaintext shown once at creation.
  • API responses never include encrypted_private_key or token hashes.

Write-tool gates

  • Capability check — Agent must have transact enabled.
  • Spending cap — Per-chain notional spend evaluated before broadcast.
  • Balance check — Native gas balance verified on the target chain.
  • Simulation — simulate_transaction dry-runs before optional broadcast.
  • Testnet rejection — Write tools reject testnet/Tenderly URLs in production configs.

Read tools

Read and compare tools incur only Pocket relay costs. They do not require funded agent wallets unless querying agent-scoped analytics.

Production checklist

  • Use strong random ENCRYPTION_KEY and JWT_SECRET
  • Keep DISABLE_AGENT_AUTH=false
  • Restrict CORS_ORIGINS to your frontend domain
  • Use HTTPS and absolute DATABASE_PATH for MCP installs