This record as markdown: /tools/io-github-kivanccakmak-yaver/git-branches.md
What git_branches does on Yaver
AI agents call git_branches 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 |
|---|---|---|---|
device_id | string | — | Optional owned Yaver agent device id/name/alias whose checkout to inspect. The /git/* routes exist on every agent, so this reads the REMOTE repository — use it |
directory | string | — |
Parameters from the server's own tool schema.
Why git_branches is rated Low
This tool performs a read-only operation—listing Git branches—with no side effects, data modification, deletion, or external execution. It is a simple informational query typical of version control inspection utilities.
From the tool's definition Tool name 'git_branches' and description 'List branches sorted by recent activity' indicate a query operation that retrieves and displays information without modifying data.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs git_branches 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_branches, this is the rule to start with:
git_branches 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_branches call is checked against it from then on.
Questions about git_branches
List branches sorted by recent activity. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_branches accepts 2 parameters: device_id, directory. 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_branches: 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_branches 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_branches 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_branches. 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_branches 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