> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/make-changes-safely/understand-read-only-and-write-operations.md). # Understand read-only and write operations Distinguish Podigee operations that inspect data from operations that can change an account. Podigee separates inspection from change. This lets a customer grant an agent useful access without automatically granting authority to publish, delete, or manage people. ## Read-only operations Read-only tools inspect current Podigee information. Examples include: * Identify the connected account and scopes. * List or inspect podcasts and episodes. * Read transcripts and generated content assets. * Review analytics and reports. * Check production, operation, and distribution status. * List private-feed listeners. The exact read scope depends on the information. Transcript access, analytics, and listeners have separate read permissions. ## Write operations Write tools can create, change, submit, upload, resume, cancel, or delete something. Examples include: * Create or update a podcast or episode. * Publish or schedule an episode. * Import a podcast. * Upload and encode media. * Submit a podcast to a supported platform. * Change feed protection or listener access. * Resume or cancel an operation. The client must have the required write scope. The Podigee account must also have access to the target resource and product capability. ## Consequential operations use confirmation Many write operations first return a dry-run preview. The preview describes the exact requested effect and returns a one-use confirmation value. The agent applies the change only after the user reviews and approves that preview. Upload-session control is an exception. It requires media write access, account ownership, and idempotency, but session creation, part control, completion, and abort do not use the preview cycle. Attaching media to an episode and publishing it retain their confirmation controls. ## Client labels are not authorization An MCP tool can tell a client that it is read-only, destructive, idempotent, or open to an external system. These annotations help the client present the action. Podigee still enforces scopes, ownership, plan access, validation, and confirmation on the server. ## Related tasks * [Preview a change before it runs](/documentation/start-here/ai-agents/make-changes-safely/preview-a-change-before-it-runs.md) * [Choose permissions and scopes](/documentation/start-here/ai-agents/connect-and-authorize/choose-permissions-and-scopes.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/documentation/start-here/ai-agents/make-changes-safely/understand-read-only-and-write-operations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.