List all files and subdirectories inside a directory.
AI agents call fs_list_directory to retrieve information from Polybridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries filesystem structure and returns information about files and directories. It performs no create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could enumerate directory contents but cannot alter data, run commands, or cause financial harm. Typical of safe Read category tools like 'ls' or 'find'.
From the tool's definition Tool name 'fs_list_directory' and description 'List all files and subdirectories inside a directory' clearly indicate a read-only operation that retrieves directory contents without modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all files and subdirectories inside a directory. It is categorised as a Read tool in the Polybridge MCP MCP Server, which means it retrieves data without modifying state.
Register the Polybridge MCP server in PolicyLayer and add a rule for fs_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 Polybridge MCP. Nothing to install.
fs_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 fs_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 fs_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.
fs_list_directory is provided by the Polybridge MCP server (madjeek-web/polybridge-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 →