This record as markdown: /tools/hybridlabor-api-aos/vault-repo-sync.md
What vault_repo_sync does on Aos
AI agents invoke vault_repo_sync to trigger actions in Aos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why vault_repo_sync is rated High
A git wrapper executes shell-level git commands (clone, pull, fetch, status, log, etc.). Even if read-mostly, executing git commands against a vault directory can have side effects such as network operations, credential access, or unintended writes. The 'Execute' category applies because it runs external operations.
From the tool's definition 'git wrapper' — executes git operations against a configured directory; 'Read-mostly' suggests primary use is read but git operations can include writes/fetches
Attacks that exploit this kind of access
The rule that runs vault_repo_sync safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vault_repo_sync, this is the rule to start with:
vault_repo_sync stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every vault_repo_sync call is checked against it from then on.
Questions about vault_repo_sync
Read-mostly git wrapper for the configured Obsidian vault directory. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for vault_repo_sync: 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 Aos. Nothing to install.
vault_repo_sync is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vault_repo_sync 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 vault_repo_sync. 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.
vault_repo_sync is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue