Read contents of multiple files at once.
AI agents call read_multiple_files to retrieve information from TermPipe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data (file contents) without side effects. It performs a query/fetch operation analogous to a basic file read command. No code execution, modification, or destructive action is implied. The severity is low because reading files alone poses minimal risk unless the files contain extremely sensitive secrets, but the tool itself has no inherent capability to cause harm—it simply retrieves information.
From the tool's definition Tool name is 'read_multiple_files' and description states 'Read contents of multiple files at once.' The verb 'read' and explicit focus on retrieving file contents with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
Read contents of multiple files at once. It is categorised as a Read tool in the TermPipe MCP MCP Server, which means it retrieves data without modifying state.
Register the TermPipe MCP server in PolicyLayer and add a rule for read_multiple_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 TermPipe MCP. Nothing to install.
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 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.
Set action: deny in the PolicyLayer 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 TermPipe MCP server (wbind-core/termpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →