git_blame

git_blame

Server TermPipe MCP wbind-core/termpipe-mcp
Category Read
Risk class Low
Parameters 00 required

What git_blame does on TermPipe MCP

AI agents call git_blame to retrieve information from TermPipe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why git_blame needs a policy

The standard 'git blame' command reads file annotation data showing which commit last modified each line — a read-only operation. However, the description is empty, so we cannot confirm the tool doesn't perform additional side effects. Given the server context (direct terminal access, execute commands), there is some risk this tool runs arbitrary git or shell commands.

From the tool's definition Tool name is 'git_blame'; description is empty and uninformative.

Questions about git_blame

What does the git_blame tool do? +

git_blame. It is categorised as a Read tool in the TermPipe MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_blame? +

Register the TermPipe MCP server in PolicyLayer and add a rule for git_blame: 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 TermPipe MCP. Nothing to install.

What risk level is git_blame? +

git_blame is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_blame? +

Yes. Add a rate_limit block to the git_blame 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.

How do I block git_blame completely? +

Set action: deny in the PolicyLayer policy for git_blame. 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.

What MCP server provides git_blame? +

git_blame is provided by the TermPipe MCP server (wbind-core/termpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.