Skip to main content
The Trip budget skill gives ChatGPT access to a scoped virtual card and its budget. It requests cards:manage, so review the card permissions before you install it. Card issuance depends on the configured issuer and your account’s eligibility.

​
What gets installed

The package requests these scopes:
  • accounts:read: read the authorized vault’s account data.
  • cards:manage: issue and manage a card.
  • payments:simulate: check a proposed payment against policy.
  • audit:stream: access the agent’s audit stream.
The package Trust preset caps are 1,000pertransactionand1,000 per transaction and 3,000 per day. Review the actual policy at installation and use limits appropriate to your trip.

​
What the agent can do

The MCP tools include accounts.balance, cards.issue, cards.freeze, payments.simulate and audit.stream. The catalog does not expose trip.list, trip.balance, trip.transactions or trip.forecast tools. The MCP card-issuance contract accepts a funding cap, merchant-category filters and an optional expiry. These are requests to the configured issuing integration, not proof of enforcement. Check which controls the issuer confirms. Consumer card controls currently reject merchant and category locks; do not assume those settings apply to every card. The skill package does not itself provide a scheduled card-revocation service.

​
Check the permissions

Start with a balance query, then review the audit feed. A read-only query does not exercise the skill’s card-management permission. Review the card and policy before authorizing spending.

​
Next