git_sync_remote
Deterministic safe sync of a remote repo: git pull --rebase --autostash against origin/<branch>, then an explicit non-force push to that origin branch. Active rebase conflicts are aborted and reported. If restoring the autostash conflicts after Git exits 0, nothing is pushed and the retained reco...
This record as markdown: /tools/io-github-kivanccakmak-yaver/git-sync-remote.md
What git_sync_remote does on Yaver
AI agents call git_sync_remote to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
work_dir | string | — | Optional repo directory to sync (default: agent work dir). |
Parameters from the server's own tool schema.
Why git_sync_remote is rated Low
Even though git_sync_remote only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs git_sync_remote safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_sync_remote, this is the rule to start with:
git_sync_remote is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every git_sync_remote call is checked against it from then on.
Questions about git_sync_remote
Deterministic safe sync of a remote repo: git pull --rebase --autostash against origin/<branch>, then an explicit non-force push to that origin branch. Active rebase conflicts are aborted and reported. If restoring the autostash conflicts after Git exits 0, nothing is pushed and the retained recovery stash + conflicted files are reported honestly. Pass work_dir for the repo to sync (defaults to the agent work dir). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_sync_remote accepts 1 parameter: work_dir. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for git_sync_remote: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Yaver. Nothing to install.
git_sync_remote is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the git_sync_remote rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for git_sync_remote. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
git_sync_remote is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue