【数据库】执行 SQLite 写入操作（INSERT/UPDATE/DELETE/CREATE/ALTER/DROP）。
AI agents call db_execute_update to permanently remove resources in LuzzyTool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly supports DROP and DELETE operations which are irreversible/destructive. It also supports DDL (CREATE/ALTER/DROP) and DML (INSERT/UPDATE/DELETE), spanning from Write to Destructive. Per the rules, the most severe applicable category is Destructive. The blast radius is critical since an AI agent could drop tables or delete all records irreversibly.
From the tool's definition 执行 SQLite 写入操作（INSERT/UPDATE/DELETE/CREATE/ALTER/DROP）
Attacks that exploit this kind of access
【数据库】执行 SQLite 写入操作（INSERT/UPDATE/DELETE/CREATE/ALTER/DROP）。. It is categorised as a Destructive tool in the LuzzyTool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for db_execute_update: 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 LuzzyTool. Nothing to install.
db_execute_update 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 db_execute_update 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 db_execute_update. 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.
db_execute_update is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). 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 →