List files in a workspace directory (restricted to workspace directory)
AI agents call list_directory_files to retrieve information from AI Development Pipeline MCP 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 without creating, modifying, deleting, or executing anything. It is a straightforward filesystem query operation with minimal blast radius—disclosure of file names within a constrained workspace poses only informational risk.
From the tool's definition Tool name 'list_directory_files' and description 'List files in a workspace directory' indicate a query/retrieval operation with no modification capability. The restriction to 'workspace directory' further limits scope.
Attacks that exploit this kind of access
List files in a workspace directory (restricted to workspace directory). It is categorised as a Read tool in the AI Development Pipeline MCP MCP Server, which means it retrieves data without modifying state.
Register the AI Development Pipeline MCP server in PolicyLayer and add a rule for list_directory_files: 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 AI Development Pipeline MCP. Nothing to install.
list_directory_files 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_files 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_files. 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_files is provided by the AI Development Pipeline MCP server (theburgerllc/ai-development-pipeline-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 →