container_file_read

Read a file or directory, returning text or a displayable base64 resource with its MIME type.

SERVERCloudflare SOURCEhttps://builds.mcp.cloudflare.com/sse

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/cloudflare/container-file-read.md

WHAT IT DOES

What container_file_read does on Cloudflare

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

RISK

Why container_file_read is rated Low

This tool retrieves file data without side effects. It is a pure read operation that queries file contents. While the sibling tools include destructive operations (container_file_delete) and writes (container_file_write), this specific tool only reads.

From the tool's definition Tool name 'container_file_read' and description 'Read a file or directory, returning text or a displayable base64 resource' explicitly indicate retrieval of file contents with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs container_file_read safely

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

container_file_read Allowed

container_file_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": {
    "container_file_read": {}
  }
}

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

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

FAQ

Questions about container_file_read

What does the container_file_read tool do? +

Read a file or directory, returning text or a displayable base64 resource with its MIME type. It is categorised as a Read tool in the Cloudflare MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on container_file_read? +

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

What risk level is container_file_read? +

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

Can I rate-limit container_file_read? +

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

Set action: deny in the PolicyLayer policy for container_file_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 container_file_read? +

container_file_read is provided by the Cloudflare MCP server (https://builds.mcp.cloudflare.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cloudflare, and thousands of servers like it.

This server

All 98 Cloudflare tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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