Read the contents of a file from the source project at: ${resolvedSourcePath}. Returns the file content as text. Use this to examine implementation details, configurations, or any text-based file.
AI agents call read_file to retrieve information from Cross-Project MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only—it reads and returns file contents without creating, modifying, executing, or deleting anything. No side effects or external operations occur. It is a straightforward read operation with minimal blast radius if misused (information disclosure is limited to file contents already in the repository).
From the tool's definition Tool name is 'read_file' and description states 'Read the contents of a file from the source project' and 'Returns the file content as text'. The verb 'Read' and 'examine implementation details' confirm retrieval without modification.
Attacks that exploit this kind of access
Read the contents of a file from the source project at: ${resolvedSourcePath}. Returns the file content as text. Use this to examine implementation details, configurations, or any text-based file. It is categorised as a Read tool in the Cross-Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cross-Project MCP Server MCP server in PolicyLayer and add a rule for read_file: 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 Cross-Project MCP Server. Nothing to install.
read_file 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_file 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_file. 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_file is provided by the Cross-Project MCP Server MCP server (sweetsrepo/cross-project-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 →