Direct answer: validate the dataset name before the agent submits it
Verified by Sanity: in MCP server version 2.31.0, create_dataset passes the dataset name to the API without normalizing it, leaving the client responsible for supplying a valid value. For deploy_schema, Sanity directs teams with an available local Studio project to work in that project’s schema files. The tool’s stated use case is a project without a local Studio.
CreatikLab’s operational interpretation is separate: do not rely on the MCP server to repair a dataset identifier, and do not make remote schema deployment the routine path when the project’s schema can be changed locally. Sanity does not give the complete naming syntax, recovery behavior or downstream consequences on this changelog page. Retrieve the applicable rules from current Sanity documentation, encode them as validation, and require evidence that the intended project and dataset were selected before approving a mutation.
