Get a summary of a GitHub repository that includes - Repo name, - Files in repo - Number of tokens in repo - Summary from the README.md Args: owner: The GitHub organization or username repo: The repository name branch: Optional branch name (default: None)
AI agents call git_summary to retrieve information from Gitingest-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that extracts and aggregates information from a GitHub repository without creating, modifying, deleting, or executing any operations. The tool has minimal blast radius if misused by an AI agent, as it only surfaces information that is typically public or accessible to the authenticated user.
From the tool's definition Tool retrieves repository metadata including repo name, files, token count, and README summary. No modifications occur—it 'Get[s] a summary' of existing public data.
Documented attack patterns abuse exactly the kind of access git_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitingest-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for git_summary:
{
"version": "1",
"default": "deny",
"tools": {
"git_summary": {}
}
}git_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a summary of a GitHub repository that includes - Repo name, - Files in repo - Number of tokens in repo - Summary from the README.md Args: owner: The GitHub organization or username repo: The repository name branch: Optional branch name (default: None). It is categorised as a Read tool in the Gitingest-MCP MCP Server, which means it retrieves data without modifying state.
Register the Gitingest- MCP server in PolicyLayer and add a rule for git_summary: 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 Gitingest-MCP. Nothing to install.
git_summary 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_summary 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_summary. 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_summary is provided by the Gitingest- MCP server (puravparab/gitingest-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Gitingest-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Gitingest-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.