Given a commit hash, returns the full story: commit message, files changed, the pull request that landed it, the PR description, and all linked GitHub issues.
AI agents call commit_story to retrieve information from Git Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only reads and assembles information from git history, pull requests, and linked issues. It performs no writes, executions, or destructive actions. The blast radius of misuse is minimal since it only exposes existing repository metadata.
From the tool's definition 'returns the full story: commit message, files changed, the pull request that landed it, the PR description, and all linked GitHub issues' — purely retrieves and aggregates existing metadata
Attacks that exploit this kind of access
Given a commit hash, returns the full story: commit message, files changed, the pull request that landed it, the PR description, and all linked GitHub issues. It is categorised as a Read tool in the Git Context MCP Server, which means it retrieves data without modifying state.
Register the Git Context MCP server in PolicyLayer and add a rule for commit_story: 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 Git Context. Nothing to install.
commit_story 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 commit_story 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 commit_story. 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.
commit_story is provided by the Git Context MCP server (muhannad-hash/git-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →