Delete an integration by ID.
AI agents call lexq_integrations_delete 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.
Deletion operations that cannot be undone fall into the Destructive category. Removing an integration could break connected workflows and business processes. The high severity reflects that integrations are often critical infrastructure; accidental deletion could cause significant operational disruption. Confidence is high because the description explicitly states deletion, which is unambiguous.
From the tool's definition Tool name 'lexq_integrations_delete' and description 'Delete an integration by ID' indicate irreversible deletion of data.
Attacks that exploit this kind of access
Delete an integration by ID. 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_integrations_delete: 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_integrations_delete 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_integrations_delete 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_integrations_delete. 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_integrations_delete 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 →