Delete an ENTIRE table from a project. The whole table area is cleared from the sheet regardless of table type, so the table no longer exists once the project is recompiled. To remove only a row or column WITHIN a table, use openl_delete_table_row / openl_delete_table_column instead. If the given...
AI agents call delete_table to permanently remove resources in Openl — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes an entire table and cannot be undone. The description explicitly states the table 'no longer exists' after deletion, making it irreversible. While the project may still compile, the data loss is complete and irrecoverable.
From the tool's definition Delete an ENTIRE table from a project. The whole table area is cleared from the sheet regardless of table type, so the table no longer exists once the project is recompiled.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete an ENTIRE table from a project. The whole table area is cleared from the sheet regardless of table type, so the table no longer exists once the project is recompiled. To remove only a row or column WITHIN a table, use openl_delete_table_row / openl_delete_table_column instead. If the given id went stale through an edit made via this server, it is resolved to the current id automatically. The studio does not auto-compile after the delete — run openl_project_status afterward to confirm the project still compiles (a dangling reference to the deleted table surfaces there). It is categorised as a Destructive tool in the Openl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Openl MCP server in PolicyLayer and add a rule for delete_table: 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 Openl. Nothing to install.
delete_table 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 delete_table 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 delete_table. 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.
delete_table is provided by the Openl MCP server (openl-mcp-server). 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 →