git_clean_preview

Preview files that

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/git-clean-preview.md

WHAT IT DOES

What git_clean_preview does on LocalAnt

AI agents call git_clean_preview to retrieve information from LocalAnt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why git_clean_preview is rated Low

The tool appears designed to preview the effects of a git clean operation (which removes untracked files) rather than execute it. Preview operations are typically read-only and non-destructive. However, confidence is moderate (0.7) because the description is incomplete ('Preview files that' cuts off), leaving some ambiguity about the actual scope and whether it might have side effects.

From the tool's definition Tool name is 'git_clean_preview' and description begins 'Preview files that' — the 'preview' verb and incomplete description suggest this is a read-only operation that shows what would be deleted without actually deleting.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_clean_preview safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_clean_preview, this is the rule to start with:

git_clean_preview Allowed

git_clean_preview is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_clean_preview": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every git_clean_preview call is checked against it from then on.

FAQ

Questions about git_clean_preview

What does the git_clean_preview tool do? +

Preview files that. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_clean_preview? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for git_clean_preview: 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 LocalAnt. Nothing to install.

What risk level is git_clean_preview? +

git_clean_preview is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_clean_preview? +

Yes. Add a rate_limit block to the git_clean_preview 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 git_clean_preview completely? +

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

git_clean_preview is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →