crow_delete_context_section
Delete a custom crow.md section. Protected sections cannot be deleted — only disabled. Scoped overrides (device/project) of protected sections CAN be deleted (restores the global version).
This record as markdown: /tools/kh0pper-crow/crow-delete-context-section.md
What crow_delete_context_section does on Crow
AI agents call crow_delete_context_section 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_delete_context_section is rated Critical
This tool irreversibly deletes data (custom crow.md sections or their scoped overrides) that cannot be restored through normal reversal operations. While some sections are protected against deletion, the tool still permits destructive removal of scoped override configurations.
From the tool's definition Tool name includes "delete" and description states "Delete a custom crow.md section". The description explicitly indicates irreversible deletion: "only disabled" for protected sections, but scoped overrides "CAN be deleted", confirming permanent removal of…
Attacks that exploit this kind of access
The rule that runs crow_delete_context_section 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_delete_context_section, this is the rule to start with:
crow_delete_context_section 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_delete_context_section call is checked against it from then on.
Questions about crow_delete_context_section
Delete a custom crow.md section. Protected sections cannot be deleted — only disabled. Scoped overrides (device/project) of protected sections CAN be deleted (restores the global version). 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_delete_context_section: 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_delete_context_section 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_delete_context_section 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_delete_context_section. 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_delete_context_section 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