Move a note to the archive folder.
AI agents use archive_note to create or update resources in Graph Rag Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Graph Rag Obsidian environment.
This operation creates a change to the note's filesystem location and metadata, making it a Write action rather than Destructive (since archiving does not delete data) or Read (since it alters state).
From the tool's definition The tool description states 'Move a note to the archive folder,' which modifies the location/state of a note but is reversible—it can be moved back from the archive.
Attacks that exploit this kind of access
Move a note to the archive folder. It is categorised as a Write tool in the Graph Rag Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Graph Rag Obsidian MCP server in PolicyLayer and add a rule for archive_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 Graph Rag Obsidian. Nothing to install.
archive_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 archive_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 archive_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.
archive_note is provided by the Graph Rag Obsidian MCP server (nickshffer/graph-rag-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 →