AI agents invoke redeploy_project to trigger actions in Openl. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Redeployment triggers an external operation that pushes a project version into a live deployment environment. This is not merely writing data — it executes a deployment pipeline with real-world effects (activating new rules, rolling back versions).
From the tool's definition Redeploy an existing deployment with a new project version. Use this to update a deployment with a newer version of the project or rollback to a previous version.
Attacks that exploit this kind of access
Redeploy an existing deployment with a new project version. Use this to update a deployment with a newer version of the project or rollback to a previous version. It is categorised as a Execute tool in the Openl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Openl MCP server in PolicyLayer and add a rule for redeploy_project: 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.
redeploy_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the redeploy_project 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 redeploy_project. 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.
redeploy_project 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 →