> ## Documentation Index > Fetch the complete documentation index at: https://docs.9pic.ai/llms.txt > Use this file to discover all available pages before exploring further. # Tools and Safeguards > Every action the 9Pic AI MCP server offers, what it changes, and when your assistant asks before acting. ## Overview The 9Pic AI MCP server gives your assistant a fixed set of tools. The assistant picks the tool your request needs; you never call them yourself. This page lists each tool so you know exactly what an assistant can and cannot do in your 9Pic account. Every tool works only on the organisations and events your dashboard role can reach. ## Read Tools These tools only read. They never change your account. | Tool | What it does | | :- | :- | | `whoami` | Shows which account is connected and which permissions you granted. | | `list_organisations` | Lists the organisations you belong to and your role in each. | | `get_plan` | Reads your current plan, credit balance and limits. The assistant checks this before the first change for an organisation. | | `list_events` | Lists the events in an organisation. | | `get_event_status` | Reads an event's details and photo progress: imported, processed, waiting and failed photos, and whether it is live. | | `get_event_settings` | Reads gallery and search settings, including whether a watermark is set up. | | `list_photo_sources` | Lists the shared folders connected to an event. | | `get_event_analytics` | Reads estimated gallery engagement for an event, optionally for a date range. | | `get_operation_status` | Checks whether an import, processing or publishing job is still running, finished or failed. | ## Change Tools These tools change your account. The assistant uses them only when you ask for that change. | Tool | What it changes | | :- | :- | | `create_event` | Creates a **draft** event with a name, date and type (running, wedding, conference or general). | | `rename_event` | Renames an event. The gallery link stays the same. | | `update_event_settings` | Changes only the settings you name: selfie search, BIB search, show all photos, timeline browsing, bulk download, photo count, and public or private visibility. | | `add_photo_source` | Connects a Google Drive, Dropbox, OneDrive or SharePoint shared folder (HTTPS link) to an event. | | `import_photos` | Imports photos from the event's photo sources. Uses no credits. | | `process_photos` | Processes a number of imported photos so participants can find them. **Spends credits after a preview and your confirmation.** | | `publish_photos` | Publishes processed photos and makes the event live for participants. | | `unpublish_photos` | Moves a live event back to draft. Participants lose access; photos and settings are kept. | ### New Event Defaults `create_event` uses the same defaults as the dashboard: selfie search on, BIB search on for running events, all photos shown with timeline browsing, bulk download on and the photo count shown. Ask the assistant to turn selfie or BIB search off when you create the event if you do not need them. ## How Processing Is Confirmed **1. Preview** The assistant asks for a preview with the number of photos you want processed. Nothing is spent yet. **2. You see the cost** The assistant tells you how many photos will actually be processed and how many credits that uses. **3. You confirm** Only after you say yes does the assistant start processing, using the exact preview you approved. A preview expires after 15 minutes. **4. Follow progress** Processing runs in the background. Ask *"Is processing finished?"* and the assistant checks the job status. > [!WARNING] > > Processing uses **1 credit per photo** when BIB search or selfie search is on, and no credits when both are off. If you do not have enough credits, processing stops and the assistant tells you. It never turns off search to save credits unless you ask. ## Other Safeguards * **Asking is not approving.** A status or readiness question never triggers a change. * **Publishing is explained first.** Before publishing, the assistant explains that participants will be able to open the gallery. Before unpublishing, it explains that access stops while photos and settings stay. * **No guessing.** If you belong to several organisations, or the event is unclear, the assistant asks you to choose. * **No duplicate jobs.** If a change's result is uncertain, the assistant checks the job status before trying again instead of repeating it. * **No purchases or upsells.** The tools cannot buy credits, change plans or open a checkout, and the assistant does not promote upgrades. * **No participant data.** Analytics are estimated totals that can be partial for some dates. They never identify participants, and missing numbers are not reported as zero. * **Your app may ask too.** Many assistants ask you to approve each change tool before it runs. You can keep that on. ## Plan Limits The tools follow your plan exactly like the dashboard: | Need | Plan | | :- | :- | | Read events, create and publish galleries | Every plan, including Trial. Trial events stay private. | | Create more than one event on a Custom plan | 9Pic AI raises the event limit (Custom plans usually cover one event) | | Process photos | Enough credits in the organisation | | Engagement analytics | Pro plan and above | ## Next Steps > **[AI Assistants (MCP)](https://docs.9pic.ai/dashboard-guide/ai-assistants.md)** > > Connect ChatGPT, Claude, Grok and other assistants. > **[Credits](https://docs.9pic.ai/dashboard-guide/credits.md)** > > How credits work and how to check your balance. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.