AI agents use notes_move to create or update resources in Macnotes — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Macnotes environment.
The tool modifies note metadata (folder location) reversibly without deleting data. This is a Write operation: it changes state but the action can be undone by moving the note to its original folder. Severity is medium because misuse could reorganize user's note structure, but notes remain intact and the action is reversible. Confidence is high due to explicit 'write' language in the description.
From the tool's definition Tool name 'notes_move' and description 'Move a note to a different folder' clearly indicates modification of note organization state. Description explicitly states '(queued background write by default)' confirming write classification.
Attacks that exploit this kind of access
Move a note to a different folder (queued background write by default). It is categorised as a Write tool in the Macnotes MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Macnotes MCP server in PolicyLayer and add a rule for notes_move: 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 Macnotes. Nothing to install.
notes_move 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 notes_move 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 notes_move. 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.
notes_move is provided by the Macnotes MCP server (zorrobyte/macnotes-mcp). 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 →