Exposed .git directory dumper
AI agents call git_dumper to retrieve information from PenTest MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and extracts data from exposed Git repositories. While it performs reconnaissance and data retrieval (Read category), the severity is high because exposing .git directories can leak sensitive information including source code, credentials, commit history, and internal development details.
From the tool's definition Tool name 'git_dumper' and description 'Exposed .git directory dumper' indicate it retrieves/dumps contents from exposed .git directories without modifying them.
Attacks that exploit this kind of access
Exposed .git directory dumper. It is categorised as a Read tool in the PenTest MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PenTest MCP Server MCP server in PolicyLayer and add a rule for git_dumper: 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 PenTest MCP Server. Nothing to install.
git_dumper 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_dumper 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_dumper. 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_dumper is provided by the PenTest MCP Server MCP server (mohitsahoo/mcptoolforwebvulnerabilities-). 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 →