Set multiple frontmatter properties on a note at once.
AI agents use obsidian_set_properties to create or update resources in Mcp Apple Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Apple Obsidian environment.
This tool creates or modifies note metadata (frontmatter properties) reversibly. It does not delete data (which would be Destructive), does not execute arbitrary code (Execute), and does not move money (Financial). The sibling tool obsidian_delete_property suggests property deletion is a separate operation, confirming this tool is Write-only.
From the tool's definition Tool description states it 'Set[s] multiple frontmatter properties on a note at once.' Setting/modifying frontmatter is a reversible modification to note metadata.
Attacks that exploit this kind of access
Set multiple frontmatter properties on a note at once. It is categorised as a Write tool in the Mcp Apple Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Apple Obsidian MCP server in PolicyLayer and add a rule for obsidian_set_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 Mcp Apple Obsidian. Nothing to install.
obsidian_set_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 obsidian_set_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 obsidian_set_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.
obsidian_set_properties is provided by the Mcp Apple Obsidian MCP server (rex/mcp-apple-obsidian). 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 →