Execute an INSERT, UPDATE, DELETE, or CREATE query
AI agents use write_query to create or update resources in SQLite MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SQLite MCP Server environment.
While DELETE is typically destructive, this tool's description groups it with INSERT, UPDATE, and CREATE, suggesting it's designed for general data manipulation rather than specifically destructive purges. DELETE without a WHERE clause could destroy data, but the tool itself is presented as a general write operation.
From the tool's definition Tool description explicitly states it executes INSERT, UPDATE, DELETE, or CREATE queries. The name 'write_query' combined with the description confirms data modification capabilities.
Attacks that exploit this kind of access
Execute an INSERT, UPDATE, DELETE, or CREATE query. It is categorised as a Write tool in the SQLite MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SQLite MCP Server 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 SQLite MCP Server. Nothing to install.
write_query is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 SQLite MCP Server MCP server (u1pns/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 →