twimco.Let’s talk ↗︎
Menu
Field notes / AI & judgment

When MCP can book or refund, name who may approve before the tool runs

The same week Flexport MCP offered create booking and Stripe MCP kept human confirmation on money moves, the operating question got clearer: write tools need a named approver before the agent can call them—not a retrospective Slack thread.

Editorial engraving of a bright meeting room where a COO places a terracotta token on a paper ladder chart while a teammate waits at his laptop.

MCP connectors that can create freight bookings, issue refunds, or otherwise change money and capacity need an authority ladder before production use. Start read-only, list every write tool, name the human who may approve each class, keep vendor confirmation features on, and ban shared logins. Flexport's booking path and Stripe's human-confirmation writes are the template—not exceptions.

The week write tools became obvious

Flexport's MCP server can create a booking against a rate—or without a rate, pending approval. Stripe's MCP server can write across a wide API surface and still requires human confirmation in the Dashboard for certain money-moving actions. ShipBob's Bobby and other ops agents have been teaching the same lesson: chat that can change the warehouse is not a novelty feature.

If the agent can write, the approval belongs in front of the tool call—not after the exception email.

This note is not a product review. It is the authority question sitting underneath the reviews. When a connector can change money, inventory, or capacity, "we'll watch the logs" is not a control.

Start read-only on purpose

Every MCP rollout wants to show a win. The win that does not create invoices is track, search, summarize, and draft. Flexport's track and rate tools, Stripe's read paths, and similar read tools in other servers are how you learn the connector's failure modes without spending.

Write tools go on a second list. Create booking, create refund, update subscription, send money—each gets a row with an owner. If you cannot name the owner, the tool stays off.

How the work moves

Authority ladder before a write tool goes live

  1. Inventory writes

    List every MCP tool that creates, updates, books, refunds, or pays.

  2. Class the risk

    Separate read, reversible write, and money/capacity write.

  3. Name the approver

    One role per class, with a backup for vacation—not a group inbox.

  4. Wire the gate

    Vendor human confirmation, client tool approval, or both—tested once.

  5. Log and revoke

    Know where tool calls appear and who can cut the connector today.

Illustrative workflow, not a client screenshot or measured result.
If the agent can write, the approval belongs in front of the tool call—not after the exception email.

Build a short authority ladder

Class 1 — Read. Anyone with a legitimate login may use these in production chats.

Class 2 — Reversible writes. Updates that can be undone quickly (draft records, tags) may run with client-side tool approval and a daily review.

Class 3 — Money and capacity. Bookings, refunds, payouts, label buys, warehouse receipts. These require a named human confirm—vendor confirmation where it exists, plus your own policy for tools that lack it.

Document the backup approver. Vacation is when unsupervised agents look attractive and when mistakes are costliest.

Keep the vendor gates on

Stripe's human confirmation is not optional theater; it is part of how MCP write safety works for user-credentialed sessions. Flexport's pending-approval booking path is a signal that even the vendor expects a human in the loop for some creates. Turning client tool-approval off to "go faster" removes the only brake some tools have.

Shared logins destroy the model. Flexport ties MCP to individual Flexport users; Stripe OAuth sessions belong to people. A single "bot" user shared in a password manager means you cannot revoke one person's access without stopping everyone—and you cannot tell who approved what.

Examples without the mythology. A freight agent that can create a booking is useful when the rate, routing, and cargo fields are validated and a named person confirms. The same agent is expensive when it books a lane from a chatty paraphrase of an email. A payments agent that can refund is useful when Stripe's human confirmation shows the amount and customer, and a lead clicks approve. The same agent is expensive when client tool-approval is off and a prompt injection rides in through a pasted ticket.

Read tools teach you whether the connector's data is trustworthy. Write tools teach you whether your organization can say no. Build the no path first.

Publish the authority ladder next to the connector enablement runbook. When someone asks to turn on booking for a demo, the ladder is the answer. If the ladder does not exist, the demo waits.

This pairs with the Flexport MCP and Stripe multi-account notes from the same daily ten: reviews tell you what the tools do; this note tells you who may let them act. Keep both in the same working folder when you brief leadership.

Write the ladder on one page. One page is enough: three classes, named approvers, backup approvers, vendor gates to leave on, and the revoke path. Tape it next to the connector enablement steps. When a vendor ships a new write tool next month, add a row before anyone demos it.

Executives who want "agentic ops" should fund the authority work the same week as the connector. Otherwise the demo becomes the production path by accident. TWIMCO's stance in AI applications and agents work is the same: useful agents start with jobs and permissions, not vibes.

If two connectors can both move money—freight booking and refunds—use one ladder language across them so staff are not learning a new dialect per vendor.

When legal or compliance asks how agents change money, hand them the ladder page and the vendor confirmation screenshots—not a slide about autonomy. Clarity beats slogans when write tools are involved.

Decision guide

Approval in front vs cleanup behind

ConsiderationApproval before the toolCleanup after the write
Human confirm on writesHuman confirms booking or refund details firstFinance discovers the booking on the invoice
Individual sign-in onlyShared login banned; individual OAuth onlyOne 'ops bot' Flexport or Stripe user everyone uses
Reads before writesRead tools live while writes stay deniedFull toolset enabled for the demo
Rehearsed revokeRevoke path rehearsedAdmin access unknown when something goes wrong
Decision framework: assess these conditions against your own agent rollout.

Put this into practice

For AI applications and agents, run a one-page workshop: list MCP write tools in use or proposed, classify them, name approvers, and test one denied write and one confirmed write. Do this before the second connector goes live, not after the third incident.

When the agent is ready to act and the org chart is not, start with that gap.

Run a tabletop exercise: the agent proposes a booking or refund while the primary approver is offline. Does the backup know how to confirm? Does the tool expire the request? Does someone unlock a shared laptop "just this once"? The exercise will reveal the real policy faster than another document draft.

Publish a one-sentence rule for vendors evaluating you: we do not enable MCP write tools without a named human confirm path. That sentence filters demos that only work with approvals disabled.

Revisit the ladder whenever a vendor adds a new write tool—booking without a rate, refund above a threshold, or money movement between balances. New tools inherit deny-by-default until a row exists. That habit is the product.

If two teams share one Flexport or Stripe org, require the ladder to name approvers per team—not a single hero who becomes the bottleneck and the single point of failure.

Store the ladder in the same folder as connector credentials requests so IT sees the human gate before provisioning access.

Deny-by-default is the only posture that survives a busy Friday.

Update the ladder the same day a new MCP write tool appears in vendor docs.

No exceptions for demos.

Rehearse the revoke path twice.

Put it in writing today.

Then enable the tool.

Related work: Spin:Market

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Spin:Market ↗︎