scrub_ignored_files

Removes files from the index that match the current .gitignore rules.

Server GitHub Auditor MCP Server westkevin12/repo-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What scrub_ignored_files does on GitHub Auditor MCP Server

AI agents call scrub_ignored_files 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.

Why scrub_ignored_files needs a policy

Removing files from the git index is a destructive action: once files are untracked and the change is committed, recovering them requires explicit git forensics. In the context of a server that also offers 'purge_history' and 'clean_repository_history', this tool fits a pattern of irreversible repository modification. An AI agent misusing this could accidentally untrack critical files across an entire repository.

From the tool's definition 'Removes files from the index that match the current .gitignore rules' — permanently removes files from the git index, which is an irreversible operation affecting repository history and tracked files.

Questions about scrub_ignored_files

What does the scrub_ignored_files tool do? +

Removes files from the index that match the current .gitignore rules. 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.

How do I enforce a policy on scrub_ignored_files? +

Register the GitHub Auditor MCP Server MCP server in PolicyLayer and add a rule for scrub_ignored_files: 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.

What risk level is scrub_ignored_files? +

scrub_ignored_files is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit scrub_ignored_files? +

Yes. Add a rate_limit block to the scrub_ignored_files 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.

How do I block scrub_ignored_files completely? +

Set action: deny in the PolicyLayer policy for scrub_ignored_files. 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.

What MCP server provides scrub_ignored_files? +

scrub_ignored_files 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.