AI agents use obsidian_set_property to create or update resources in Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian environment.
This tool modifies note metadata by setting or creating frontmatter properties. While modifications are reversible (can be edited/removed), the operation creates or overwrites structured data. This is clearly a Write operation rather than Read (it modifies rather than just retrieves). It is not Destructive because the changes are reversible and do not permanently delete data.
From the tool's definition Tool description states it 'Sets a frontmatter property on a note' and 'Creates the frontmatter block if missing.' The frontmatter property setting is a modification operation that alters note metadata reversibly.
Attacks that exploit this kind of access
Sets a frontmatter property on a note. Creates the frontmatter block if missing. It is categorised as a Write tool in the Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP server in PolicyLayer and add a rule for obsidian_set_property: 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. Nothing to install.
obsidian_set_property 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 obsidian_set_property 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 obsidian_set_property. 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.
obsidian_set_property is provided by the Obsidian MCP server (yuchi-chang/obsidian-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 →