crow_data_write
Execute a write SQL statement (INSERT, CREATE TABLE, UPDATE, DELETE) on a user-owned database. Separate from read-only queries for safety.
This record as markdown: /tools/kh0pper-crow/crow-data-write.md
What crow_data_write does on Crow
AI agents call crow_data_write to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crow_data_write is rated Critical
The tool explicitly supports DELETE statements, which are irreversible destructive operations. It also supports INSERT, UPDATE, and CREATE TABLE. Because DELETE is permitted and represents the most severe operation in the set, this tool must be classified as Destructive. The blast radius is critical since an AI agent could DROP or DELETE arbitrary data from a user-owned database.
From the tool's definition Execute a write SQL statement (INSERT, CREATE TABLE, UPDATE, DELETE) on a user-owned database
Attacks that exploit this kind of access
The rule that runs crow_data_write safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_data_write, this is the rule to start with:
crow_data_write 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 Crow, apply this rule, and every crow_data_write call is checked against it from then on.
Questions about crow_data_write
Execute a write SQL statement (INSERT, CREATE TABLE, UPDATE, DELETE) on a user-owned database. Separate from read-only queries for safety. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_data_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 Crow. Nothing to install.
crow_data_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 crow_data_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 crow_data_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.
crow_data_write is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
Across the catalogue