Execute an INSERT, UPDATE, or DELETE query on the SQLite database
AI agents call write_query to permanently remove resources in Server Puppeteer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly executes INSERT, UPDATE, and DELETE queries on a database. DELETE operations are irreversible and destructive. Even INSERT/UPDATE can cause significant data corruption or loss. The most severe applicable category is Destructive due to the DELETE capability. Critical severity because an AI agent could wipe or corrupt entire database tables.
From the tool's definition Execute an INSERT, UPDATE, or DELETE query on the SQLite database
Attacks that exploit this kind of access
Execute an INSERT, UPDATE, or DELETE query on the SQLite database. It is categorised as a Destructive tool in the Server Puppeteer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Server Puppeteer MCP server in PolicyLayer and add a rule for write_query: 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 Server Puppeteer. Nothing to install.
write_query 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 write_query 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 write_query. 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.
write_query is provided by the Server Puppeteer MCP server (@hisma/server-puppeteer). 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 →