List files and directories in the source project at: ${resolvedSourcePath}. Returns names, types (file/directory), and sizes. Automatically excludes common non-essential directories like node_modules and .git.
AI agents call list_directory to retrieve information from Cross-Project MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
list_directory performs a directory listing operation that queries and returns filesystem metadata. It has no side effects: it neither modifies data, executes code, deletes content, nor moves money. The automatic exclusion of certain directories is a filtering feature, not a modification. This is a straightforward Read operation with minimal security risk when properly scoped to the source project path.
From the tool's definition Tool description states it "List files and directories" and "Returns names, types (file/directory), and sizes." The verb "list" and the read-only nature of the operation—returning metadata about filesystem structure without modification—clearly indicate a…
Attacks that exploit this kind of access
List files and directories in the source project at: ${resolvedSourcePath}. Returns names, types (file/directory), and sizes. Automatically excludes common non-essential directories like node_modules and .git. It is categorised as a Read tool in the Cross-Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cross-Project MCP Server MCP server in PolicyLayer and add a rule for list_directory: 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 Cross-Project MCP Server. Nothing to install.
list_directory 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_directory 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_directory. 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_directory is provided by the Cross-Project MCP Server MCP server (sweetsrepo/cross-project-mcp). 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 →