Read the contents of multiple files simultaneously. This is more efficient than reading files one by one when you need to analyze or compare multiple files. Each file's content is returned with its path as a reference. Failed reads for individual files won't stop the entire operation. Only works ...
Bulk/mass operation — affects multiple targets
Part of the Filesystem MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call read_multiple_files to retrieve information from Filesystem without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though read_multiple_files only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
read_multiple_files:
rules:
- action: allowSee the full Filesystem policy for all 14 tools.
Agents calling read-class tools like read_multiple_files have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Read the contents of multiple files simultaneously. This is more efficient than reading files one by one when you need to analyze or compare multiple files. Each file's content is returned with its path as a reference. Failed reads for individual files won't stop the entire operation. Only works within allowed directories.. It is categorised as a Read tool in the Filesystem MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for read_multiple_files. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Filesystem MCP server.
read_multiple_files 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 read_multiple_files rule in your Intercept 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 Intercept policy for read_multiple_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.
read_multiple_files is provided by the Filesystem MCP server (@modelcontextprotocol/server-filesystem). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept