Delete a fact definition. System facts cannot be deleted.
AI agents call lexq_facts_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.
This tool permanently removes fact definitions from the business rules system. Deletion is irreversible and has broad blast radius—fact definitions are foundational data structures that policies and rules depend on. Removing a fact definition could break dependent rules, A/B tests, or deployments.
From the tool's definition Tool is named 'lexq_facts_delete' with description stating it 'Delete[s] a fact definition.' The verb 'delete' and the description's explicit use of 'Delete' indicate irreversible removal of data.
Attacks that exploit this kind of access
Delete a fact definition. System facts cannot be deleted. 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_facts_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_facts_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_facts_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_facts_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_facts_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 →