Managing access usage and limits

Everything lives on Settings → Integrations → Model Context Protocol.

Connected AI Clients

Each assistant you approved appears with its name and when it was last used. Revoke signs it out: it can no longer reach the project until someone connects it again.

API Keys

Each key shows its name, who created it, its Client ID, and, after a rotation, how long the previous secret remains valid. The menu offers Rotate, Retire previous secret, and Revoke. Details on API Keys for Automations.

Changing What an Assistant May Do

Connect the assistant again with the same URL. The approval page lists what it already has and what approving adds.

New permissions reach existing assistants the same way. An assistant connected before October 7, 2026 gets Build and run my Jimo Agent only after you connect it again and approve it.

To take a permission away, revoke the client, then connect again with fewer boxes ticked.

Usage & Limits

Reading is free. Overviews, funnels, feedback, agent test questions, and previews do not count. Reads are rate-limited to keep the service fair, never metered.

Only executed changes count. Your plan includes a monthly allowance of AI-driven changes, and a change is charged only once it has succeeded:

Confirmed change	Cost
Publish, pause, deletion, audience change	1 unit
Saved custom answer, agent setting change	1 unit
Page, skill, or knowledge source created	1 unit each
Translation	1 unit per language written
Document import	1 unit per document

A change that fails, is refused, or repeats an earlier identical call costs nothing. A batch the project cannot afford is refused whole at preview time and writes nothing.

When the allowance is used up, changes are refused with a "monthly change limit reached" message. Reading keeps working, and the allowance resets with your billing cycle.

Every change result reports what it cost and what remains, so your assistant can warn you when you are getting close to the limit.

Next Steps

• Troubleshooting: what the limit and permission messages look like, and what to do.

• Permissions & Safety: the full safety model.