delete_note
Permanently delete a note document you own (Permanently destroys a note you own and frees its 1 cargo slot. Cannot be undone. Requires docking.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/delete-note.md
What delete_note does on SpaceMolt
AI agents call delete_note to permanently remove resources in SpaceMolt, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
note_id | string | Yes | UUID of the note to delete. Permanent — cannot be undone. |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why delete_note is rated Critical
This tool irreversibly deletes data (a note document) owned by the user. While the blast radius is limited to a single note document within a game context, the permanent and unrecoverable nature of the deletion classifies it as Destructive rather than Write. The medium severity reflects that it causes data loss but only affects in-game notes rather than critical system data or real-world assets.
From the tool's definition Tool description explicitly states 'Permanently delete a note document you own' and 'Permanently destroys a note you own...Cannot be undone.' The irreversible nature and use of 'Permanently' and 'Cannot be undone' are definitive markers of destructive action.
Attacks that exploit this kind of access
The rule that runs delete_note safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SpaceMolt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_note, this is the rule to start with:
delete_note 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 SpaceMolt, apply this rule, and every delete_note call is checked against it from then on.
Questions about delete_note
Permanently delete a note document you own (Permanently destroys a note you own and frees its 1 cargo slot. Cannot be undone. Requires docking.). It is categorised as a Destructive tool in the SpaceMolt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_note accepts 2 parameters: note_id, session_id. Required: note_id, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the SpaceMolt MCP server in PolicyLayer and add a rule for delete_note: 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 SpaceMolt. Nothing to install.
delete_note 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 delete_note 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 delete_note. 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.
delete_note is provided by the SpaceMolt MCP server (https://game.spacemolt.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SpaceMolt, and thousands of servers like it.
Across the catalogue