Accept an MCP tool's new definition

POST /v1/mcp-servers/{mcp_server_id}/tools/{tool_name}/accept

Pins the latest listed definition of an allowed tool at the revision If-Match names and answers the registration (1.60.0; mcp-client.md section 3). Agent versions keep the pin they froze: after a contract change the tool stays refused with schema_drift until a new Agent version is published with the accepted pin. A tool the latest listing lacks is not_found, from 1.61.0 with one detail mcp_tool_not_listed at /tool_name that tells it from an unknown registration (a 422 would change the status 1.60.0 answers, ADR 0029 rule 3); one that is not allowed is validation_failed with mcp_tool_not_allowed. Writes an Audit event naming the tool and both digests.

Request

Set VOCAL_API to the base URL of your API and VOCAL_API_KEY to an API key with the mcp:write scope (Authentication and keys). Replace each placeholder, such as agt_... or <name>, with your own value.

curl -X POST "$VOCAL_API/v1/mcp-servers/mcps_.../tools/<tool_name>/accept" \
  -H "Authorization: Bearer $VOCAL_API_KEY" \
  -H 'If-Match: "1"' \
  -H "Idempotency-Key: $(uuidgen)"

const response = await fetch(`${process.env.VOCAL_API}/v1/mcp-servers/mcps_.../tools/<tool_name>/accept`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.VOCAL_API_KEY}`,
    'If-Match': '"1"',
    'Idempotency-Key': crypto.randomUUID(),
  },
});
console.log(response.status, await response.text());

import os
import uuid

import requests

response = requests.post(
    f"{os.environ['VOCAL_API']}/v1/mcp-servers/mcps_.../tools/<tool_name>/accept",
    headers={
        "Authorization": f"Bearer {os.environ['VOCAL_API_KEY']}",
        "If-Match": '"1"',
        "Idempotency-Key": str(uuid.uuid4()),
    },
)
print(response.status_code, response.text)

Parameters

Responses

Fields of the 200 answer

The shape is McpServer.