minds_deleteMind
Delete an owned Mind (controller lifecycle action delete) without an automatic retry (DELETE /v1/minds/services/{mind_id})
This record as markdown: /tools/onesi-genesis-mcp/minds-deletemind.md
What minds_deleteMind does on Genesis
AI agents call minds_deleteMind to permanently remove resources in Genesis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
mind_id | string | Yes | |
idempotency_key | string | Yes | Persisted UUID4 for this lifecycle intent. Retain it with the original expected_generation after uncertainty. |
expected_generation | integer | Yes | Original desired_generation from a fresh owned read; keep unchanged with the idempotency key if outcome is unknown. |
Parameters from the server's own tool schema.
Why minds_deleteMind is rated Critical
An AI agent that decides to call minds_deleteMind doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Genesis is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs minds_deleteMind safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For minds_deleteMind, this is the rule to start with:
minds_deleteMind 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 Genesis, apply this rule, and every minds_deleteMind call is checked against it from then on.
Questions about minds_deleteMind
Delete an owned Mind (controller lifecycle action delete) without an automatic retry (DELETE /v1/minds/services/{mind_id}). It is categorised as a Destructive tool in the Genesis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
minds_deleteMind accepts 3 parameters: mind_id, idempotency_key, expected_generation. Required: mind_id, idempotency_key, expected_generation. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for minds_deleteMind: 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 Genesis. Nothing to install.
minds_deleteMind 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 minds_deleteMind 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 minds_deleteMind. 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.
minds_deleteMind is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
Across the catalogue