patch_v1_git_repos_name
Flips a repo's public bit, the one mutable repo setting today.
Flips a repo's public bit, the one mutable repo setting today. Public grants ANONYMOUS fetch only; push and the whole control plane stay org-authed. Returns the updated repo.
| Tool | patch_v1_git_repos_name |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2 |
| Operation | PATCH /v1/git/repos/{name} |
| Product | git |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
name | string | — | — | Name is the repo to update, from the :name path segment. |
public | boolean | — | — | Public flips anonymous read access. Omit it and the request is refused — there is nothing else to update yet. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "patch_v1_git_repos_name",
"arguments": {
"name": "<name>",
"public": false
}
}
}'Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_patch_v1_git_repos_name | PATCH /v1/git/repos/{name} | git | Flips a repo's public bit, the one mutable repo setting today. |
The same capability over plain HTTP is in the git API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?