List available repositories discovered in the current directory
AI agents call list 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 tool performs a read-only operation that enumerates repositories. It has no side effects, does not execute code, does not modify data, and does not involve financial operations. The blast radius of misuse is minimal—an AI agent could only discover information already accessible in the current directory structure. Classification as Read is appropriate.
From the tool's definition Tool name 'list' and description 'List available repositories discovered in the current directory' indicates a query/discovery operation that retrieves information about repositories without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List available repositories discovered in the current directory. 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 list: 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.
list 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 list 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 list. 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.
list 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 →