Soft-delete a billing import batch and its truth rows. Use to clean up stale or test imports. The batch can be re-imported afterward.
AI agents call l6e_delete_billing_batch to permanently remove resources in L6e — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although described as a 'soft-delete' (potentially recoverable), the tool irreversibly removes billing import batches and their associated truth rows from the system. Billing data is critical financial information. Misuse by an AI agent could lead to loss of billing records, audit trail corruption, or incorrect cost tracking.
From the tool's definition Tool name includes 'delete' and description states 'Soft-delete a billing import batch and its truth rows.' The action removes billing records, which are financial data.
Attacks that exploit this kind of access
Soft-delete a billing import batch and its truth rows. Use to clean up stale or test imports. The batch can be re-imported afterward. It is categorised as a Destructive tool in the L6e MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the L6e MCP server in PolicyLayer and add a rule for l6e_delete_billing_batch: 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 L6e. Nothing to install.
l6e_delete_billing_batch 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 l6e_delete_billing_batch 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 l6e_delete_billing_batch. 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.
l6e_delete_billing_batch is provided by the L6e MCP server (l6e-ai/l6e-mcp). 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 →