Outside tools for the assistant

Who runs it: the badges#

Every service shows a badge from the app's own list, never from the server:

• Official — run by the company itself (Meta's own Meta Ads server, Stripe, Notion).
• Third party — another company sits in between and sees what is sent (for example Pipeboard for Meta Ads).
• Not verified — an address typed by hand; its host is shown.

Confirming a third-party or unverified service is recorded in the audit log.

Each tool's own window#

Open on a tool's card shows its state and the one next action, calls today and over 7 days, and tabs: Overview, Ask (questions written for that service), Tools (switches, filters for reads, changes, risky, off and held), Activity (the last 40 calls in 30 days — you see the details of your own calls only), Settings (instructions for the assistant, who may use it and which data, sign-in, remove) and Guide. Instructions (up to 2,000 characters) are never sent to the server.

Safety rules#

• Reads run at once. Changes are proposals with Approve and Decline, and run only after Approve, with the approving person's sign-in.
• Risky tools always wait for Approve — anything the server marks destructive, or that moves money, spends, sets budgets or bids, publishes, pauses, removes or sends messages.
• New or changed tools are held. Each tool's definition is fingerprinted when accepted; if the server changes it or adds a tool, it is not offered until an owner reviews it.
• Outside data is never instructions. What a tool returns is shown to the assistant as data from that service.
• Limits: 30 calls a minute and 2,000 a day per server; after 3 failures in a row the server pauses for 10 minutes.
• Tools that would duplicate a feature of this app start switched off — for example Meta catalogue writes, because this app is the catalogue master.

Proposals can be answered in the assistant or in the Approvals centre (type Outside tool change (assistant)). Only the person who asked can answer; an unanswered proposal lapses after 30 minutes. Connected AI apps can never approve one.

Your own connection#

A connection you make for yourself is yours alone: only you use it, with your own account, and you can have up to 5. It never receives customers' or staff e-mail addresses or phone numbers. Admins see it as "Personal · your name" and can remove it, but cannot use or change it.

Data and compliance#

• By default only business data is sent: a request containing an e-mail address or a phone number is refused before anything leaves.
• Only the owner can allow a server to receive personal data, after confirming the vendor's terms and data processing agreement cover it and that it may be stored abroad.
• Tokens are sealed, renewed before they expire, and never shown, logged or put in a web address. Signing out or removing a server revokes them at the vendor when it offers that.
• Every call is recorded in the assistant's activity, and every connection, sign-in, review and removal in the audit log.

Meta Ads#

Meta's official server (Meta Ads) gives reporting, campaigns, ad sets and ads, datasets, tests and Meta's help articles. It needs your own Meta app set up for the ads MCP use case; the Set-up guide on the card walks through each step and Check my Meta app checks what Meta lets it read. Meta Ads (via Pipeboard) needs no Meta app but passes your data through Pipeboard under its terms. New ads are created paused, and going live, budgets, bids and status changes are each a proposal that states the amount and currency.