AI agents call read_project_file to retrieve information from Openl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file contents from a project without modifying, deleting, or executing anything. The GET mapping and 'Read' verb in both name and description confirm this is a data retrieval operation with no side effects. Low severity because reading files alone does not cause damage, though sensitive file contents could be exposed depending on access controls.
From the tool's definition Tool name is 'read_project_file' and description explicitly states 'Read any file in a project' with 'Maps to GET /projects/{projectId}/files/{path}'. GET is an HTTP method for retrieval with no side effects.
Attacks that exploit this kind of access
Read any file in a project by its project-relative path — text or binary, and folder listings too. Maps to GET /projects/{projectId}/files/{path}. Behavior by path/params:. It is categorised as a Read tool in the Openl MCP Server, which means it retrieves data without modifying state.
Register the Openl MCP server in PolicyLayer and add a rule for read_project_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 Openl. Nothing to install.
read_project_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_project_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_project_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_project_file is provided by the Openl MCP server (openl-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 →