AI agents use remnote_move_note to create or update resources in Remnote — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remnote environment.
This tool creates a structural modification (moving notes and their children to a new parent location) but does not delete, destroy, or irreversibly alter data. The operation is reversible—notes can be moved back to their original location. This places it in the Write category rather than Destructive.
From the tool's definition Tool description states it will 'move an existing Rem and its subtree under a new parent,' which modifies the hierarchical structure and location of data within the knowledge base.
Attacks that exploit this kind of access
Safely move an existing Rem and its subtree under a new parent. Defaults to dryRun=true; pass dryRun=false only after user approval. expectedOldParentRemId rejects stale move proposals. It is categorised as a Write tool in the Remnote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remnote MCP server in PolicyLayer and add a rule for remnote_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 Remnote. Nothing to install.
remnote_move_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the remnote_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 remnote_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.
remnote_move_note is provided by the Remnote MCP server (remnote-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →