fs_read

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-read.md

WHAT IT DOES

What fs_read does on Container-MCP

AI agents call fs_read 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_read is rated Low

File read operations are inherently non-destructive and produce no side effects beyond data retrieval. Despite the empty description, the naming convention and context from sibling tools make it clear this retrieves file contents without modification. Classified as Read with low severity due to sandbox constraints and lack of write/execute capabilities.

From the tool's definition Tool name is 'fs_read' which indicates file system read operation. The server description emphasizes 'safe' and 'sandboxed' execution. Sibling tools like 'fs_write', 'fs_delete', 'fs_list' confirm this tool operates in a file system context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fs_read 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_read, this is the rule to start with:

fs_read Allowed

fs_read 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_read": {}
  }
}

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_read call is checked against it from then on.

FAQ

Questions about fs_read

What does the fs_read tool do? +

fs_read 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_read? +

Register the Container MCP server in PolicyLayer and add a rule for fs_read: 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_read? +

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

Can I rate-limit fs_read? +

Yes. Add a rate_limit block to the fs_read 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_read completely? +

Set action: deny in the PolicyLayer policy for fs_read. 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_read? +

fs_read 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

binary_read on 010 Editor → The MCP Attack Database →

Guides

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