AI agents use create_project_branch to create or update resources in Openl — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openl environment.
Creating a project branch is a write operation that adds new data to the system. It is reversible (the branch can be deleted), has limited blast radius when misused by an agent, and does not execute arbitrary code, delete data irreversibly, or move money. Severity is low because branch creation in a rules management system typically has minimal downstream impact without subsequent deployments or modifications.
From the tool's definition Tool name 'create_project_branch' and description 'Create a new branch in a project' indicate creation of a new project branch, a reversible data structure operation.
Attacks that exploit this kind of access
Create a new branch in a project. It is categorised as a Write tool in the Openl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Openl MCP server in PolicyLayer and add a rule for create_project_branch: 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.
create_project_branch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_project_branch 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 create_project_branch. 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.
create_project_branch 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 →