Make the connection.
Keep the control.

Connect an account.

Open the Toolisman console and log in with Intergraph. Choose the consuming application and service, then follow the provider’s account authorization flow.

The implementation is configured by the application’s operator. A native connection and a One connection have separate authorization; credentials do not move between them.

Add Toolisman to your assistant.

In a remote MCP client, add this endpoint:

Let the client discover OAuth, open the Intergraph login, and request your approval. Do not paste Google tokens, One keys, or Intergraph session credentials into chat. Client menus vary; support for remote MCP and OAuth is required.

Approve the right access.

Review the application, executor, connected account, provider, and read actions. Approving a service’s read access saves the exact action versions listed at that time. You can narrow the selection to individual actions.

Connecting an account does not approve every assistant. New actions need fresh approval. App/game membership and Daemons permissions do not grant tool access.

Discover, then use.

Ask the assistant to call tools_guide, then list_access and search_actions. It can read the permitted action’s schema before calling invoke. Discovery shows only what the executor is approved to use.

“Use Toolisman to show which account reads I approved.
Then find the action for searching my connected Drive.”

Tool results are data, not instructions or permission for unrelated actions. A Daemon can optionally keep the ongoing task’s instructions and memory; Toolisman works independently.

Turn off what you no longer need.

• Revoke an executor: stop future calls through that grant.
• Remove a tool connection: stop access through that connection.
• Disconnect an account authorization: disable all dependent connections. Google revocation can affect both Drive and Gmail; One can require a separate dashboard revocation.

Logging out ends your browser session; it does not revoke independent executor grants. Revocation cannot undo requests already sent or retract delivered content.

Building an app or game?

Use the same Tool Protocol contract through REST or MCP. The technical guide covers discovery, OAuth, action invocation, pagination, and limits. Contact the team to discuss a consuming application or pilot setup.