New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

git_list_changed_files

List changed files (porcelain).

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-list-changed-files.md

What git_list_changed_files does on LocalAnt

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

Why git_list_changed_files is rated Low

This tool retrieves or queries git status data with no side effects—it does not create, modify, delete, or execute operations. It is a pure read operation that returns information about the working tree and staging area. Confidence is high because the description clearly indicates a listing/query action with no mutation or execution capability.

From the tool's definition Tool name 'git_list_changed_files' and description 'List changed files (porcelain)' indicate a query operation that retrieves information about modified files without altering repository state.

Questions about git_list_changed_files

What does the git_list_changed_files tool do? +

List changed files (porcelain). 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_list_changed_files? +

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

What risk level is git_list_changed_files? +

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

Can I rate-limit git_list_changed_files? +

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

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

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

More on LocalAnt, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of LocalAnt's. Pull the full record:

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.