Read multiple files at once. Returns concatenated content with headers.
AI agents call read_multiple_files to retrieve information from Cursor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs data retrieval only—reading and concatenating file contents—with no ability to modify, delete, or execute code. It is a passive query operation similar to 'get' or 'fetch' operations. While it could expose sensitive code or data if an AI agent is misused, the tool itself is not dangerous; the risk is in what data exists in the workspace.
From the tool's definition Tool name is 'read_multiple_files' and description states it 'Read multiple files at once. Returns concatenated content with headers.' This is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Read multiple files at once. Returns concatenated content with headers. It is categorised as a Read tool in the Cursor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cursor MCP Server 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 Cursor MCP Server. 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 Cursor MCP Server MCP server (tariqnasheed/cursor_mcp_server). 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 →