List files and directories in a repository.
AI agents call ls to retrieve information from MCP Build Environment Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a standard directory listing operation that queries data about file system structure. It has no capability to modify, delete, or execute anything—purely informational retrieval. The blast radius if misused is minimal, as an AI agent gaining directory listings poses no immediate danger to the system or data integrity.
From the tool's definition Tool name 'ls' and description 'List files and directories in a repository' indicate a read-only operation that retrieves directory contents without modification or side effects.
Attacks that exploit this kind of access
List files and directories in a repository. It is categorised as a Read tool in the MCP Build Environment Service MCP Server, which means it retrieves data without modifying state.
Register the MCP Build Environment Service MCP server in PolicyLayer and add a rule for ls: 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 MCP Build Environment Service. Nothing to install.
ls 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 ls 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 ls. 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.
ls is provided by the MCP Build Environment Service MCP server (jbroll/mcp-build). 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 →