Skip to content

v1.2.0

Choose a tag to compare

@ryanmichaeljames ryanmichaeljames released this 11 May 00:41
· 67 commits to main since this release
134d90d

Added

  • DATAVERSE_ALLOW_WRITE and DATAVERSE_ALLOW_DELETE environment variables to gate write and delete tool registration at server startup — when not set, those tools are not exposed to the agent at all

Changed

  • Write tools (dataverse_associate_records, dataverse_merge_records, all create/update schema tools) now require DATAVERSE_ALLOW_WRITE=true in the MCP server env to be registered
  • dataverse_execute_batch is always registered for GET-only batch usage; non-GET operations in a batch now require DATAVERSE_ALLOW_WRITE=true
  • Delete tools (dataverse_disassociate_records, dataverse_delete_table, dataverse_delete_column, dataverse_delete_relationship, dataverse_delete_choice, dataverse_delete_choice_option) now require DATAVERSE_ALLOW_DELETE=true in the MCP server env to be registered

Removed

  • BREAKING: Per-call allow_write and allow_delete parameters removed from all write and delete tool inputs — access is now controlled entirely by the MCP server env flags
  • BREAKING: Preview mode removed from all write and delete tools