Your agent just approved a $47,500 wire transfer.
It matched the vendor. The amount was within policy. The invoice looked real. So the agent executed it. No pause, no review, no record of why. Turns out it was a spoofed invoice. Nobody caught it until reconciliation.
Auto-approved: $47,500.00 → vendor_acme_8291 → executed 0.4sWhat if it didn't just execute? What if it paused?
One wrapper. Zero architecture changes.
Wrap any function with guard(). Below a threshold, it passes through. Above it, Meshgate pauses execution and routes the decision to a human. The agent picks back up once they approve.
import { MeshgateClient } from '@meshgate/sdk'
const meshgate = new MeshgateClient({
apiKey: process.env.MESHGATE_API_KEY,
localEncryptionKey: process.env.MESHGATE_LOCAL_SECRET,
})
// Wrap once. Your agent calls it normally.
const processPayment = meshgate.guard(executePayment, {
intent: 'process_payment',
getIntentArgs: (vendor, amount) => ({ vendor, amount }),
})
// $47,500 triggers a gate. $200 passes through.
await processPayment('acme-corp', 47500)
That same $47,500. This time, with a gate.
Watch the payment get stopped, reviewed, and approved.
The payload gets encrypted right on the agent's machine. The intent is registered with Meshgate. A human reviews the details and approves. Then the agent picks back up with a one-time verification token. Proof of exactly who said yes.
Your agent's machine
intentprocess_payment
amount$47,500
payloadencrypting...
fnexecutePayment()...
Meshgate cloud
intentprocess_payment
amount$47,500
agentagt_payments
SC
Sarah Chen
Finance Lead · reviewing now
Encrypting payload locally
One function guarded. Now picture an entire pipeline.
Gates drop into any workflow.
Receive. Enrich. Gate. Execute. Audit. The approval step slots in wherever a human decision matters. Meshgate pauses the pipeline, notifies the right person, and picks back up when they decide.
GateSC
Sarah Chen
Finance Lead · reviewing
Local AES-256-GCM
Your arguments never leave your environment unencrypted.
Atomic token burn
Each token works once, then it's gone. No replays.
Per-gate key derivation
Every gate gets its own key. One compromised gate can't touch the rest.
Phone-home verification
Your agent doesn't guess. It waits for a confirmed decision before it moves.
Cold resume
If the process restarts, pending approvals pick up where they left off.
Configurable policies
Auto-approve the low-risk stuff. Require sign-off on the rest. Your call.
The gate fires. A human decides. The agent picks back up. But making the right call isn't enough on its own. You need to prove it happened.