Delete a webhook subscription by ID.
AI agents call lexq_webhook_subscriptions_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.
Deleting a webhook subscription is a destructive action that removes integration configuration permanently and cannot be undone. While not directly impacting financial transactions or primary data, it disrupts operational integrations and could cause cascading failures if triggered inappropriately. The action is irreversible, placing it in the Destructive category rather than Write.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a webhook subscription by ID.' This is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a webhook subscription 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_webhook_subscriptions_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_webhook_subscriptions_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_webhook_subscriptions_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_webhook_subscriptions_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_webhook_subscriptions_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 →