AI agents use lexq_versions_clone to create or update resources in LexQ — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LexQ environment.
This tool creates a new version by duplicating an existing one. Creation of new configuration/version objects is a Write operation. It is not Read (no side effects), not Execute (doesn't run arbitrary code), not Destructive (the clone can be removed), and not Financial.
From the tool's definition Tool description states 'Clone an existing version to create a new DRAFT', which involves creating a new data structure (a cloned version). The action is reversible—the cloned draft can be deleted or discarded.
Attacks that exploit this kind of access
Clone an existing version to create a new DRAFT. Useful when the source version is already published. It is categorised as a Write tool in the LexQ MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LexQ MCP server in PolicyLayer and add a rule for lexq_versions_clone: 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_versions_clone 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 lexq_versions_clone 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_versions_clone. 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_versions_clone 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 →