List local change history for a project. Returns list of workspace history items with versions, authors, timestamps, and comments. NOTE: Requires the project to be opened (openl_open_project first); not available for repository
AI agents call list_project_local_changes 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 queries and retrieves historical metadata (versions, authors, timestamps, comments) from an already-opened project without making any changes. It is a read-only operation with no side effects, fitting the Read category with low severity since it only exposes audit/history information.
From the tool's definition Tool name and description indicate it 'List local change history' and 'Returns list of workspace history items' — pure data retrieval with no modification, deletion, execution, or financial impact.
Attacks that exploit this kind of access
List local change history for a project. Returns list of workspace history items with versions, authors, timestamps, and comments. NOTE: Requires the project to be opened (openl_open_project first); not available for repository. 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 list_project_local_changes: 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.
list_project_local_changes 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 list_project_local_changes 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 list_project_local_changes. 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.
list_project_local_changes 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 →