Git integration for vibe coding sessions. Get repository status, commit history, diffs, branch info. Capture git snapshots for sessions and extract design decisions from commit messages.
Accepts file system path (path); High parameter count (25 properties)
Part of the Vibe Coding MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call muse_git to retrieve information from Vibe Coding without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though muse_git only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
muse_git:
rules:
- action: allowSee the full Vibe Coding policy for all 15 tools.
Agents calling read-class tools like muse_git have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Git integration for vibe coding sessions. Get repository status, commit history, diffs, branch info. Capture git snapshots for sessions and extract design decisions from commit messages.. It is categorised as a Read tool in the Vibe Coding MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for muse_git. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Vibe Coding MCP server.
muse_git 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 muse_git rule in your Intercept 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 Intercept policy for muse_git. 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.
muse_git is provided by the Vibe Coding MCP server (vibe-coding-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept