AI agents call repo_list_files to retrieve information from Git Steer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read-only operation that retrieves directory contents from a repository. It has no side effects, does not modify data, execute code, or trigger external operations. The blast radius of misuse is minimal—an adversary could enumerate repository structure but cannot access file contents, modify files, or trigger actions. Classification as Read with low severity is appropriate.
From the tool's definition Tool name 'repo_list_files' and description 'List files in a repository directory' indicate a query operation that retrieves file listings without modifying data.
Attacks that exploit this kind of access
List files in a repository directory. It is categorised as a Read tool in the Git Steer MCP Server, which means it retrieves data without modifying state.
Register the Git Steer MCP server in PolicyLayer and add a rule for repo_list_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 Git Steer. Nothing to install.
repo_list_files 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 repo_list_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.
Set action: deny in the PolicyLayer policy for repo_list_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.
repo_list_files is provided by the Git Steer MCP server (ry-ops/git-steer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
repo_list_files is one line of Git Steer's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →