Update frontmatter properties of a note.
AI agents use update_note_properties 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 tool creates or modifies data reversibly by updating note metadata. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial operations.
From the tool's definition Tool name 'update_note_properties' combined with description 'Update frontmatter properties of a note' indicates modification of metadata. Frontmatter (YAML/toml at file start) is structured, reversible data that can be edited or reverted.
Attacks that exploit this kind of access
Update frontmatter properties of a note. 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 update_note_properties: 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.
update_note_properties 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 update_note_properties 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 update_note_properties. 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.
update_note_properties 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 →