This record as markdown: /tools/io-github-portel-dev-ncp/write-query.md
What write_query does on Ncp
AI agents call write_query to permanently remove resources in Ncp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why write_query is rated Critical
This tool explicitly supports DELETE operations which are irreversible data destruction, as well as INSERT and UPDATE. Since the most severe applicable category applies, and DELETE is a destructive operation, this is classified as Destructive. An AI agent could misuse this to delete arbitrary records or tables. The severity is critical due to the broad blast radius of arbitrary write/delete SQL access.
From the tool's definition Execute an INSERT, UPDATE, or DELETE query
Attacks that exploit this kind of access
The rule that runs write_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For write_query, this is the rule to start with:
write_query is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every write_query call is checked against it from then on.
Questions about write_query
Execute an INSERT, UPDATE, or DELETE query. It is categorised as a Destructive tool in the Ncp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ncp 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 Ncp. 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 Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
Across the catalogue