テンプレートを使用してObsidianノートを作成します
AI agents use create_note_from_template to create or update resources in Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
This tool creates new notes in an Obsidian vault, which is a reversible modification of the vault's data structure. It does not delete or irreversibly destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or simply read data (Read).
From the tool's definition Tool name 'create_note_from_template' and server description explicitly states 'note creation from templates' as a core function. The Japanese description translates to 'Create Obsidian notes using templates,' confirming data creation capability.
Attacks that exploit this kind of access
テンプレートを使用してObsidianノートを作成します. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for create_note_from_template: 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 MCP Server. Nothing to install.
create_note_from_template 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 create_note_from_template 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 create_note_from_template. 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.
create_note_from_template is provided by the Obsidian MCP Server MCP server (libra850/obsidian-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 →