vault_git
Run git push, pull, fetch, clone, or ls-remote over SSH with a vaulted key kept in the broker; only approved servers can connect.
Instructions
Run git push, pull, fetch, clone or ls-remote over SSH with a vaulted SSH key that never leaves the broker. Every address git would connect to (including a separate push address and any rewrite in git config) must be a server approved for the entry, or nothing connects; for a key saved without servers, the first use of a new server asks the owner. Only SSH remotes; no submodules, no hooks during the run. Linux and macOS only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"entry_id": "<entry_id>",
"purpose": "<purpose>",
"subcommand": "<subcommand>",
"repo_dir": "<repo_dir>"
},
"name": "vault_git"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | clone only: the SSH address, e.g. git@github.com:owner/repo.git. | |
| flags | No | Allowed: push --force-with-lease --tags --set-upstream --dry-run --delete --follow-tags; pull --ff-only --rebase --no-rebase; fetch --tags --prune --dry-run --depth=N; clone --depth=N --branch=NAME --single-branch --no-checkout; ls-remote --heads --tags. | |
| remote | No | Named remote, e.g. origin. Required except for clone. | |
| purpose | Yes | Why (activity log). | |
| entry_id | Yes | Vault entry holding the SSH key. | |
| refspecs | No | push/pull/fetch: branches or refspecs, e.g. ["main"]. | |
| repo_dir | Yes | The local repository (for clone: the folder to clone into). | |
| subcommand | Yes | ||
| target_dir | No | clone only: folder name to create inside repo_dir. | |
| timeout_seconds | No | Default 120, at most 870. |