gitleaks
Runs Gitleaks to detect hardcoded secrets in git repositories. Returns structured finding data with redacted secrets.
This record as markdown: /tools/io-github-dave-london-pare-test/gitleaks.md
What gitleaks does on Test
AI agents invoke gitleaks to trigger actions in Test. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why gitleaks is rated High
The tool executes an external security scanning binary (Gitleaks) against git repositories. While its intent is defensive (secret detection), it runs arbitrary code against repositories and could be pointed at sensitive codebases to enumerate secret locations. Classified as Execute because it triggers an external process whose effects depend on arguments (which repository to scan).
From the tool's definition Runs Gitleaks to detect hardcoded secrets in git repositories
Attacks that exploit this kind of access
The rule that runs gitleaks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitleaks, this is the rule to start with:
gitleaks stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Test, apply this rule, and every gitleaks call is checked against it from then on.
Questions about gitleaks
Runs Gitleaks to detect hardcoded secrets in git repositories. Returns structured finding data with redacted secrets. It is categorised as a Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Test MCP server in PolicyLayer and add a rule for gitleaks: 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 Test. Nothing to install.
gitleaks is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gitleaks 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 gitleaks. 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.
gitleaks is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Test, and thousands of servers like it.
This server
Across the catalogue