Set a frontmatter property on a note
AI agents use property_set to create or update resources in Obsidian Local — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Local environment.
This tool modifies frontmatter properties (metadata) within Obsidian notes. Frontmatter properties are YAML key-value pairs at the top of markdown files. Setting properties is reversible—an agent can set them to different values, delete them, or revert changes. This is a Write operation, not Destructive, since the action can be undone.
From the tool's definition Tool name 'property_set' and description 'Set a frontmatter property on a note' indicate modification of note metadata. The verb 'set' combined with 'frontmatter property' confirms this creates or modifies data reversibly.
Attacks that exploit this kind of access
Set a frontmatter property on a note. It is categorised as a Write tool in the Obsidian Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Local MCP server in PolicyLayer and add a rule for property_set: 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 Obsidian Local. Nothing to install.
property_set 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 property_set 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 property_set. 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.
property_set is provided by the Obsidian Local MCP server (matthewsuazo/obsidian-local-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 →