maker_delete_learner
Permanently delete a learner and cascade to sessions, transcripts, memories, and storage references. Tier-1 destructive action — admin confirms in panel before calling.
This record as markdown: /tools/kh0pper-crow/maker-delete-learner.md
What maker_delete_learner does on Crow
AI agents call maker_delete_learner 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 maker_delete_learner is rated Critical
This tool irreversibly deletes data (learner profile and all associated sessions, transcripts, memories, storage) with no undo capability. The cascading nature means deletion propagates to dependent records. Described as 'Tier-1 destructive action', confirming its critical destructive status. The high blast radius (complete loss of learner data and history) and irreversibility justify critical severity.
From the tool's definition Tool description states: 'Permanently delete a learner and cascade to sessions, transcripts, memories, and storage references' — the words 'permanently delete' and 'cascade' confirm irreversible deletion across multiple related entities.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs maker_delete_learner 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 maker_delete_learner, this is the rule to start with:
maker_delete_learner 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 maker_delete_learner call is checked against it from then on.
Questions about maker_delete_learner
Permanently delete a learner and cascade to sessions, transcripts, memories, and storage references. Tier-1 destructive action — admin confirms in panel before calling. 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 maker_delete_learner: 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.
maker_delete_learner 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 maker_delete_learner 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 maker_delete_learner. 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.
maker_delete_learner 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