SQLite 데이터베이스에서 테이블을 삭제합니다. DROP TABLE 명령을 실행합니다.
AI agents call delete_table to permanently remove resources in SQLite MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation that cannot be undone. It destroys data at scale (entire table) rather than individual rows. The critical severity reflects the potential for catastrophic data loss if an AI agent misuses this tool without confirmation—dropping the wrong table or all tables in a database. This is the most severe category applicable.
From the tool's definition Tool name 'delete_table' and description states it 'executes DROP TABLE command' on SQLite databases. DROP TABLE irreversibly removes an entire table structure and all data within it.
Attacks that exploit this kind of access
SQLite 데이터베이스에서 테이블을 삭제합니다. DROP TABLE 명령을 실행합니다. It is categorised as a Destructive tool in the SQLite MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SQLite MCP Server 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 SQLite MCP Server. 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 SQLite MCP Server MCP server (yuchoe/sqlite-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 →