List files and directories in a given path. Paths are relative to the parent repository root.
AI agents call list_directory to retrieve information from Z Ai Integration MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and lists filesystem information with no side effects. It does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an attacker could only gain knowledge of the filesystem structure, which is a read-only operation.
From the tool's definition Tool name 'list_directory' and description 'List files and directories in a given path' indicate a query operation that retrieves directory contents without modification or execution.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List files and directories in a given path. Paths are relative to the parent repository root. It is categorised as a Read tool in the Z Ai Integration MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Z Ai Integration 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 Z Ai Integration 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 Z Ai Integration MCP Server MCP server (williamlebrato/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 →