move_note
Move a note to a different folder. NOTE: Apple Notes has no native move command, so this copies the note body to the target folder and deletes the original. The note will get a new ID and creation date. Attachments (images) will be lost.
This record as markdown: /tools/io-github-heznpc-iconnect/move-note.md
What move_note does on Iconnect
AI agents call move_note to permanently remove resources in Iconnect, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why move_note is rated Critical
The tool irreversibly deletes the original note and permanently loses all attachments during the move operation. Data loss (attachments) cannot be undone, and the original note identity (ID, creation date) is destroyed, making this Destructive rather than merely Write.
From the tool's definition copies the note body to the target folder and deletes the original. The note will get a new ID and creation date. Attachments (images) will be lost.
Attacks that exploit this kind of access
The rule that runs move_note safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_note, this is the rule to start with:
move_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 Iconnect, apply this rule, and every move_note call is checked against it from then on.
Questions about move_note
Move a note to a different folder. NOTE: Apple Notes has no native move command, so this copies the note body to the target folder and deletes the original. The note will get a new ID and creation date. Attachments (images) will be lost. It is categorised as a Destructive tool in the Iconnect MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Iconnect MCP server in PolicyLayer and add a rule for move_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 Iconnect. Nothing to install.
move_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 move_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 move_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.
move_note is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue