MCP Mutation and Version-Selection Behavior
MCP tools can read resources, run workflows, or change configuration. Review the selected operation and version before a call that changes data.

Example request within an initialized MCP session. projects_get reads configuration; it does not execute the project. Version fields differ between tools—check the discovered schema.
Before you begin
An authenticated MCP client with the required tool and resource permissions.
Key concepts
Read-only mode
A server configuration that limits available operations to supported non-mutating capabilities. Discover the actual tool set; execution and mutation tools can be absent.
Project version
A specific saved configuration of a project. Select it explicitly when a result must be reproducible.
Side effect
A change outside the returned answer, such as creating a record or sending email. Cancellation or release rollback does not undo a completed side effect.
Revision conflict
A response indicating that the resource changed since the version used for an edit. Read current state and reconcile changes before resubmitting.
Configuration options
Dry run
A supported preview or validation option that avoids applying the selected change.
Its scope belongs to the specific operation; it is not a universal parameter.
Select a version for an MCP operation
Read the tool’s schema and select the intended organization and project.
Set its supported version and publication options explicitly where needed.
Inspect the returned result and read the resource again after a change.
The tool performs the intended operation against the intended resource version.
Behavior and limitations
Read-only configurations can omit mutation and execution tools. A dry-run option applies only where the specific tool supports it. A project run and a project edit are different operations. Use the selected tool’s version contract rather than assuming REST selector values apply unchanged.
Related resources
Was this helpful?

