{% extends "docs/base.html" %}
{% block docs_content %}
<h1 class="h3 mb-2">Lock tools</h1>
<p>The MCP server exposes <code>acquire_lock</code>, <code>get_lock_ticket</code>, <code>heartbeat_lock_ticket</code>, and <code>release_lock_ticket</code>.</p>
<div class="alert alert-info mb-4" role="note">
  Learn the ownership boundaries in the <a href="/docs/guides/locks">Lease locks guide</a>, then see
  <a href="/docs/guides/coordinate-concurrent-agents">how duplicate responders coordinate</a>.
</div>
<pre><code>{
  "lock_name": "deploy",
  "request_uuid": "e41b7608-1fe8-4f54-a5f3-67e8605f480c",
  "lease_seconds": 60,
  "wait_seconds": 30,
  "repo": "teams/platform/app"
}</code></pre>
<p>Omit both <code>team</code> and <code>repo</code> for your user scope. Pass the returned <code>ticket_uuid</code>, same <code>lock_name</code>, and same scope to poll, heartbeat, or release.</p>
<p><code>heartbeat_lock_ticket</code> accepts <code>lease_seconds</code> from 5-300 and defaults to 60.</p>
<p>Waiters are FIFO and report exact queue position. A promoted holder receives a globally increasing fence token. Use it as an atomic stale-writer check in the protected system; Pearing does not terminate external work when a lease expires.</p>
{% endblock %}