This record as markdown: /tools/io-github-kivanccakmak-yaver/git-reflog.md
What git_reflog does on Yaver
AI agents call git_reflog 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 |
|---|---|---|---|
count | integer | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why git_reflog is rated Low
Git reflog is a diagnostic/informational command that queries the local Git repository's undo history. It does not create, modify, delete, or execute any operations—it merely displays metadata about past Git operations. This is a purely read-based tool with minimal security risk.
From the tool's definition Tool name is 'git_reflog' and description states 'Show reflog (undo history)'. The reflog command displays Git's reference logs which record when refs were updated.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs git_reflog 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_reflog, this is the rule to start with:
git_reflog 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_reflog call is checked against it from then on.
Questions about git_reflog
Show reflog (undo history). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_reflog accepts 2 parameters: count, 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_reflog: 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_reflog 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_reflog 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_reflog. 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_reflog 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