Map of Contents(目次ノート)を自動生成します
AI agents use create_moc 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.
The tool creates a new note (Map of Contents) in the Obsidian vault. This is a Write operation as it creates new data reversibly—the generated MOC can be edited or deleted. It is not Read-only (retrieves data), not Execute (does not run arbitrary code), not Destructive (content can be recovered), and not Financial.
From the tool's definition Tool name 'create_moc' combined with description indicating automatic generation of 'Map of Contents' note. This is a file creation operation that modifies the vault by adding new content.
Attacks that exploit this kind of access
Map of Contents(目次ノート)を自動生成します. 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_moc: 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_moc 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_moc 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_moc. 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_moc 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.
create_moc is one line of Obsidian MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →