read_files

Read multiple files in one call using glob patterns. Useful for quickly attaching context without many read_file calls.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/read-files.md

WHAT IT DOES

What read_files does on CoWork OS

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

RISK

Why read_files is rated Low

This tool retrieves file contents without modifying, deleting, or executing anything. It is a straightforward read operation that gathers context. While it could expose sensitive data if an agent specifies overly broad glob patterns, the tool itself performs no destructive or executable actions. The blast radius is limited to information disclosure, making it low severity.

From the tool's definition Tool name is 'read_files' and description states it 'Read multiple files in one call using glob patterns.' The verb 'read' and the explicit statement that it reads files confirms retrieval-only functionality with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_files safely

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

read_files Allowed

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

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

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

FAQ

Questions about read_files

What does the read_files tool do? +

Read multiple files in one call using glob patterns. Useful for quickly attaching context without many read_file calls. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_files? +

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

What risk level is read_files? +

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

Can I rate-limit read_files? +

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

How do I block read_files completely? +

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

What MCP server provides read_files? +

read_files is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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