fs_list

A read tool on the Container- MCP server.

SERVERContainer-MCP SOURCE54rt1n/container-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54rt1n-container-mcp/fs-list.md

WHAT IT DOES

What fs_list does on Container-MCP

AI agents call fs_list to retrieve information from Container-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why fs_list is rated Low

Despite empty description, the name 'fs_list' strongly indicates a read-only filesystem operation that retrieves directory contents or file metadata without modifying data. This aligns with 'Read' category as it queries information with no side effects. Confidence reduced from 0.95 to 0.85 due to missing description, but the context and naming convention make the classification highly reliable.

From the tool's definition Tool name 'fs_list' indicates filesystem listing operation. Combined with sibling tools (fs_read, fs_write, fs_delete, fs_move) in a filesystem API, this tool clearly performs a directory/file listing query with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fs_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Container-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fs_list, this is the rule to start with:

fs_list Allowed

fs_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fs_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Container-MCP, apply this rule, and every fs_list call is checked against it from then on.

FAQ

Questions about fs_list

What does the fs_list tool do? +

fs_list is a read tool on the Container MCP server. It is categorised as a Read tool in the Container-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fs_list? +

Register the Container MCP server in PolicyLayer and add a rule for fs_list: 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 Container-MCP. Nothing to install.

What risk level is fs_list? +

fs_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fs_list? +

Yes. Add a rate_limit block to the fs_list 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.

How do I block fs_list completely? +

Set action: deny in the PolicyLayer policy for fs_list. 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.

What MCP server provides fs_list? +

fs_list is provided by the Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Container, and thousands of servers like it.

This server

All 27 Container tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →