Early access

A policy layer and kill switch for AI agent wallets, exposed as an MCP server.

It enforces limits outside the model, at the signing layer, so an agent cannot talk its way past them. It works with any framework through MCP and replaces no agent.

Launch app Read the docs

Core features: 5
Status: Early access
Network: Solana
Your funds: Non-custodial

MCP server with request_action, check_policy and get_budget tools that any agent framework can callPolicy editor: per-action cap, daily budget, token and program allowlists, active hours, all signed by the owner walletTransaction simulation before approval, with a plain-language reason for every block or passLive action feed per agent with one-click pause and a Telegram alert when a rule tripsDelegate mode: a capped delegate key funded by the owner, so the owner never hands over the main wallet

Live action feed

Time	Agent	Action	Amount	Verdict	Reason
14:02	dca-bot	Swap USDC to SOL via Jupiter	25 USDC	Passed	Under the 50 USDC per-action cap, progra
13:47	treasury-scout	Transfer to 4nHc...Tq9e	1.5 SOL	Blocked	Destination is not on the recipient allo
13:31	arb-watcher	Swap SOL to JitoSOL	0.8 SOL	Passed	Simulation shows output within 0.4% of q
12:58	dca-bot	Swap USDC to SOL via Jupiter	25 USDC	Passed	Daily budget at 75 of 200 USDC
12:20	arb-watcher	Call unknown program 8vQe...mR2k	0.3 SOL	Blocked	Program is not on the allowlist
11:44	payroll-agent	Transfer USDC to Dk3x...W7ba	120 USDC	Held	Above 100 USDC cap, waiting for owner ap
03:12	dca-bot	Swap USDC to SOL via Jupiter	25 USDC	Blocked	Outside active hours (08:00 to 22:00 UTC

Agents

dca-botDelegate key 6bQw...Zr4s, 0.9 SOL leftActive
treasury-scoutDelegate key Gm2P...c8Hd, 3 blocks todayActive
arb-watcherPaused by owner at 12:21Paused
payroll-agent1 action waiting for approvalNeeds review

Rules on dca-bot

Per-action cap 50 USDC

Daily budget 200 USDC

Active hours 08:00 to 22:00 UTC

Jupiter only program allowlist

The parts that do the work.

Built for builders shipping agents that touch funds, DAOs and funds testing agent treasuries, and power users running personal trading or DCA agents.

Agents

dca-botDelegate key 6bQw...Zr4s, 0.9 SOL leftActive
treasury-scoutDelegate key Gm2P...c8Hd, 3 blocks todayActive
arb-watcherPaused by owner at 12:21Paused
payroll-agent1 action waiting for approvalNeeds review

MCP server with request_action, check_policy and get_budget tools that any agent framework can call

Planned

Rules on dca-bot

Per-action cap 50 USDC

Daily budget 200 USDC

Active hours 08:00 to 22:00 UTC

Jupiter only program allowlist

Policy editor: per-action cap, daily budget, token and program allowlists, active hours, all signed by the owner wallet

Planned

Transaction simulation before approval, with a plain-language reason for every block or pass

Planned

Budget today

3.4 of 8SOL spent

195 of 400USDC spent

6Rules tripped

4Telegram alerts sent

Live action feed per agent with one-click pause and a Telegram alert when a rule trips

Planned

Delegate mode: a capped delegate key funded by the owner, so the owner never hands over the main wallet

Planned

Policy editor: per-action cap, daily budget, token and program allowlists, active hours, all signed by the owner wallet.

Per-action caps, daily budgets, token and program allowlists and active hours. Each change is signed in Phantom, Solflare or Backpack, so the policy cannot be edited by the agent.

Planned

Policy for dca-bot

Rule	Value	Scope	Signed by
Per-action cap	50 USDC	Every request	9rTq...1vBo
Daily budget	200 USDC	Resets 00:00 UTC	9rTq...1vBo
Token allowlist	USDC, SOL	Swaps and transfers	9rTq...1vBo
Program allowlist	Jupiter v6	Any instruction	9rTq...1vBo
Active hours	08:00 to 22:00 UTC	Daily	9rTq...1vBo

MCP server with request_action, check_policy and get_budget tools that any agent framework can call.

Point your agent at Tripwire and it gets three tools: request_action, check_policy and get_budget. Nothing about your agent changes except where it asks before it signs.

Planned

mcp config for your agent

json

{
  "mcpServers": {
    "tripwire": {
      "command": "npx",
      "args": ["@tripwire/mcp", "--agent", "dca-bot"],
      "env": {
        "TRIPWIRE_OWNER": "9rTqW4kVx2mNbHc7aZsE5dJf8LpYu3GwQeXtK6Rn1vBo",
        "TRIPWIRE_RPC": "https://api.mainnet-beta.solana.com"
      }
    }
  }
}

Transaction simulation before approval, with a plain-language reason for every block or pass.

Before approving, Tripwire simulates the transaction and compares it with the policy. The verdict is written in plain language so you can see why, not just what.

Planned

arb-watcher asks, Tripwire answers

request_action: send 0.3 SOL to program 8vQe...mR2k

Blocked. Simulation succeeds, but program 8vQe...mR2k is not on this agent's allowlist. No funds moved.

request_action: swap 0.8 SOL to JitoSOL on Jupiter

Passed. Simulated output is 0.4% under quote, the cap is 1 SOL, and Jupiter is allowlisted. Signing now.

Live action feed per agent with one-click pause and a Telegram alert when a rule trips.

Each agent has its own feed. When a rule trips you get a Telegram message, and one click pauses the agent until you say otherwise.

Planned

Recent trips

treasury-scout tried an unlisted recipient13:47, 1.5 SOL, Telegram alert sentBlocked
arb-watcher called an unknown program12:20, auto-paused after 2nd tripPaused
payroll-agent exceeded per-action cap11:44, 120 USDC, awaiting youHeld
dca-bot ran outside active hours03:12, 25 USDCBlocked

Delegate mode: a capped delegate key funded by the owner, so the owner never hands over the main wallet.

Fund a capped delegate key from the owner wallet and give that key to the agent. If something goes wrong, the loss is limited to what the delegate holds.

Planned

Set up a delegate for dca-bot

Create the delegateTripwire generates key 6bQw...Zr4s and registers it under your owner wallet.

Fund itSend 1 SOL and 200 USDC from the owner wallet, sized to the daily budget.

Sign the policyApprove the rules in your wallet. Requests outside them are never signed.

Top up or revokeRefill when the feed shows low balance, or revoke and sweep funds back in one tr

It enforces limits outside the model, at the signing layer, so an agent cannot talk its way past them. It works with any framework through MCP and replaces no agent.

3 steps from start to first result.

Connect your agentAdd the Tripwire MCP server to your agent framework and give it a delegate key i

Sign your rulesSet caps, budgets, allowlists and hours, then sign the policy with Phantom, Solf

Let it run, stay in controlEvery action is simulated and checked at the signing layer. You see the reason f

Open by default.

Every screen reads from the same model. Live parts read public onchain data; nothing ever asks your wallet to sign.

Read the docs

tripwire.json

{
  "product": "Tripwire",
  "network": "solana",
  "features": [
    {
      "name": "MCP server with request_action, check_policy and",
      "status": "planned"
    },
    {
      "name": "Policy editor: per-action cap, daily budget, tok",
      "status": "planned"
    },
    {
      "name": "Transaction simulation before approval, with a p",
      "status": "planned"
    },
    {
      "name": "Live action feed per agent with one-click pause ",
      "status": "planned"
    }
  ]
}

What works today.

Live features work today. Planned ones are next on the roadmap, in this order.

MCP server with request_action, check_policy and get_budget tools that any agent framework can callPlanned

Policy editor: per-action cap, daily budget, token and program allowlists, active hours, all signed by the owner walletPlanned

Transaction simulation before approval, with a plain-language reason for every block or passPlanned

Live action feed per agent with one-click pause and a Telegram alert when a rule tripsPlanned

Delegate mode: a capped delegate key funded by the owner, so the owner never hands over the main walletPlanned

Questions.

Short answers. The docs have the rest.

What is Tripwire?

A policy layer and kill switch for AI agent wallets, exposed as an MCP server. It enforces limits outside the model, at the signing layer, so an agent cannot talk its way past them. It works with any framework through MCP and replaces no agent.

What works today?

Tripwire is in development. Every feature is on the status list with what ships next, and the app opens in a sample workspace so you can see how it will work.

Do I need a wallet?

No. You can explore without one. Connecting a Solana wallet only shares your public address so Tripwire can read your balances; it never asks you to sign a transaction.

Who is it for?

Builders shipping agents that touch funds, DAOs and funds testing agent treasuries, and power users running personal trading or DCA agents.

MCP server with request_action, check_policy and get_budget tools that any agent framework can call.

A policy layer and kill switch for AI agent wallets, exposed as an MCP server.

Launch app Read the docs