AI agents call git_steer_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 tool performs a straightforward directory listing operation on a GitHub repository, returning file and directory information without side effects. It is a read-only query operation that retrieves repository structure metadata. No data is modified, created, deleted, or executed.
From the tool's definition Tool name contains 'list' and description states 'List files and directories at a path' — a pure retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
List files and directories at a path in a GitHub repository. 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 git_steer_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.
git_steer_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 git_steer_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 git_steer_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.
git_steer_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.
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 →