Connect a developer's Stripe account to their tru app via Stripe Connect OAuth. Works with the app's API key — no admin key needed. Both test and live mode use real OAuth — the developer connects their own Stripe account either way. NEVER say 'no browser needed' or 'automatic' or 'a test account ...
AI agents use dev_connect_stripe to create or update resources in Tru — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tru environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | Stripe mode: 'test' connects the developer's Stripe test environment (no real money), 'live' connects for real payments. Both use OAuth. IMPORTANT: Always ask t |
service_name | string | — | The service_name of the app to connect. If omitted, uses the app from ~/.tru/config.json (set by dev_register_app). |
Parameters from the server's own tool schema.
This tool establishes an OAuth connection between a developer's Stripe account and the tru platform. It creates a new persistent integration/authorization relationship (Write), but does not itself move money or commit financial obligations — it only links accounts. However, misuse could grant unauthorized access to a Stripe account, enabling future financial operations, hence high severity.
From the tool's definition Connect a developer's Stripe account to their tru app via Stripe Connect OAuth
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Connect a developer's Stripe account to their tru app via Stripe Connect OAuth. Works with the app's API key — no admin key needed. Both test and live mode use real OAuth — the developer connects their own Stripe account either way. NEVER say 'no browser needed' or 'automatic' or 'a test account will be created' — both test and live mode open a browser for Stripe Connect OAuth. There is NO shortcut. In test mode, both tru and the developer's app use Stripe's test environment: no real money moves, charges show up in the developer's Stripe test dashboard, and test cards (4242...) are used. In live mode, real payments are processed. IMPORTANT: Before calling this tool, ASK the developer whether they want to connect in test or live mode. Explain: test mode connects their Stripe account's test environment (no real money, charges visible in their Stripe test dashboard, test cards), live mode connects for real payments. Both require Stripe OAuth authorization in the browser. If they don't specify, ask — do NOT default silently. Pass their choice as the mode parameter. Tell the user: 'Opening your browser for Stripe Connect authorization — complete the process there and I\'ll continue automatically when it\'s done.' For test mode, add: 'Make sure you\'re in test mode on the Stripe OAuth page (you should see a test mode banner).' This tool blocks while waiting for the user to finish in the browser. It is categorised as a Write tool in the Tru MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dev_connect_stripe accepts 2 parameters: mode, service_name. The full parameter table on this page comes from the server's own tool schema.
Register the Tru MCP server in PolicyLayer and add a rule for dev_connect_stripe: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Tru. Nothing to install.
dev_connect_stripe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dev_connect_stripe rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for dev_connect_stripe. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
dev_connect_stripe is provided by the Tru MCP server (tru-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →