Artifact locks
An edit lock marks an artifact as being edited by one user, so that two users do not overwrite each other’s work. Lock tools let an AI assistant check who is already editing an artifact, lock an artifact while it works on it, and remove the lock afterwards. The same locks are shown in the Lock Entries tool of the Cockpit.
For artifact types that use edit locks, saving, deleting, or activating an artifact through the MCP server respects a lock that another user holds. The call fails with an error that names the lock and the time since when it has been held.
Required role: locking.
Remove a lock that another user holds
delete_lock also removes a lock that another user holds. In that case, the removal
is written to the audit log with
the object type Lock, and the response names the user who held the lock and
since when.
| A lock protects changes that its holder has not saved yet. Remove another user’s lock only after you have agreed on it with that user. |
Available tools
| Tool | Description | Parameters |
|---|---|---|
|
List the edit locks that are currently held, newest first. Without field selection,
each entry contains |
|
|
Lock an artifact for editing by you. The response has the status |
|
|
Remove the lock on an artifact. If you hold the lock, it is released. If another user holds it, it is removed and the removal is audited. If the artifact is not locked, nothing happens. |
|
Related topics
-
Tools overview — the full list of artifact types and required roles.
-
Access control — how role, development package, and lock checks are enforced on every tool call.