AI agents invoke write-query to trigger actions in SQLite MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name 'write-query' strongly implies execution of data-modifying SQL statements (INSERT, UPDATE, DELETE). Given the sibling tool 'read-query' handles SELECT statements, this tool likely executes write-side SQL. Since it could include DELETE/DROP statements, it spans Execute to Destructive, but without a description confirming irreversible deletion, Execute is the most defensible classification.
From the tool's definition Tool name 'write-query' on a SQLite MCP server described as enabling users to 'run SQL queries'. Sibling tool 'read-query' exists, implying this tool handles non-read (INSERT/UPDATE/DELETE) SQL operations.
Documented attack patterns abuse exactly the kind of access write-query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SQLite MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for write-query:
{
"version": "1",
"default": "deny",
"tools": {
"write-query": {
"limits": [
{
"counter": "write-query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}write-query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
write-query. It is categorised as a Execute tool in the SQLite MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
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 Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 (jacksteamdev/mcp-sqlite-bun-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SQLite MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 SQLite MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.