squash_noise_commits
AI agents call squash_noise_commits to permanently remove resources in GitHub Auditor MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Squashing commits is a destructive git operation that rewrites commit history, permanently removing individual commits. The sibling tools on this server (purge_history, clean_repository_history, scrub_ignored_files) all perform irreversible history modifications, strongly suggesting this tool does the same.
From the tool's definition Tool name 'squash_noise_commits' and server context involving 'clean_repository_history', 'purge_history', 'scrub_ignored_files' — all destructive git history operations. Squashing commits rewrites/removes git history irreversibly.
Attacks that exploit this kind of access
squash_noise_commits. It is categorised as a Destructive tool in the GitHub Auditor MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub Auditor MCP Server MCP server in PolicyLayer and add a rule for squash_noise_commits: 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.
squash_noise_commits is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the squash_noise_commits 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 squash_noise_commits. 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.
squash_noise_commits 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 →