Rollback to the previous deployed version. Only available if there is a previous version.
AI agents call lexq_deploy_rollback to permanently remove resources in LexQ — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Rolling back a deployment overwrites the current live configuration with a previous version, irreversibly discarding the current deployment state. This is a destructive operation from the perspective of the current deployed version — it cannot be undone without re-deploying. The blast radius is high because it affects live business rules in production.
From the tool's definition Rollback to the previous deployed version
Attacks that exploit this kind of access
Rollback to the previous deployed version. Only available if there is a previous version. It is categorised as a Destructive tool in the LexQ MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LexQ MCP server in PolicyLayer and add a rule for lexq_deploy_rollback: 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 LexQ. Nothing to install.
lexq_deploy_rollback is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the lexq_deploy_rollback 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 lexq_deploy_rollback. 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.
lexq_deploy_rollback is provided by the LexQ MCP server (lexq-io/lexq-cli). 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 →