Run INSERT, UPDATE, DELETE and other destructive SQL queries on the connected database. Use with caution as this can modify data.
AI agents call query_write to permanently remove resources in MCP Universal DB Client — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly supports DELETE queries (irreversible data removal) alongside INSERT and UPDATE. Since it permits destructive SQL operations like DELETE (and potentially DROP/TRUNCATE via 'other destructive SQL queries'), it falls into the Destructive category.
From the tool's definition 'Run INSERT, UPDATE, DELETE and other destructive SQL queries' and 'this can modify data'
Attacks that exploit this kind of access
Run INSERT, UPDATE, DELETE and other destructive SQL queries on the connected database. Use with caution as this can modify data. It is categorised as a Destructive tool in the MCP Universal DB Client MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Universal DB Client MCP server in PolicyLayer and add a rule for query_write: 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 MCP Universal DB Client. Nothing to install.
query_write 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 query_write 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 query_write. 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.
query_write is provided by the MCP Universal DB Client MCP server (izumisy/mcp-universal-db-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
query_write is one line of MCP Universal DB Client's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →