Deep-scans the entire commit history for leaked API keys, passwords, and .env files using TruffleHog.
AI agents call audit_secrets to retrieve information from GitHub Auditor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only scan/audit of the repository's commit history to detect secrets. It does not modify, delete, or execute anything — it retrieves and reports findings. However, severity is medium because it accesses highly sensitive data (API keys, passwords, .env files) across the entire commit history, meaning a misuse or exfiltration of results could cause significant harm.
From the tool's definition Deep-scans the entire commit history for leaked API keys, passwords, and .env files using TruffleHog
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Deep-scans the entire commit history for leaked API keys, passwords, and .env files using TruffleHog. It is categorised as a Read tool in the GitHub Auditor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Auditor MCP Server MCP server in PolicyLayer and add a rule for audit_secrets: 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 GitHub Auditor MCP Server. Nothing to install.
audit_secrets 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 audit_secrets 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 audit_secrets. 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.
audit_secrets is provided by the GitHub Auditor MCP Server MCP server (westkevin12/repo-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 →