List files and directories at a given path with metadata.
AI agents call list_directory to retrieve information from DevToolkit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves directory contents and their metadata. It performs a read-only query of the filesystem without creating, modifying, deleting, or executing anything. The action is informational with no blast radius if misused by an AI agent—at worst it reveals filesystem structure the agent already has access to.
From the tool's definition Tool name 'list_directory' and description 'List files and directories at a given path with metadata' indicate retrieval of filesystem information with no modification or side effects.
Attacks that exploit this kind of access
List files and directories at a given path with metadata. It is categorised as a Read tool in the DevToolkit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevToolkit 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 DevToolkit 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 DevToolkit MCP Server MCP server (tusharrayamajhi/devtoolkit-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 →