Import all markdown files from a folder
AI agents use import_markdown_folder 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 or adds new notes/files to the knowledge base, which is a write operation. It has moderate severity because bulk imports could flood a vault with unwanted content, but the operation is reversible and does not permanently destroy data or execute arbitrary code. Confidence is high because the intent is clear from the name and description.
From the tool's definition Tool name 'import_markdown_folder' and description 'Import all markdown files from a folder' indicate creation/addition of markdown content into the Obsidian vault. The action is reversible (imported files can be deleted or the vault state reverted).
Documented attack patterns abuse exactly the kind of access import_markdown_folder gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for import_markdown_folder:
{
"version": "1",
"default": "deny",
"tools": {
"import_markdown_folder": {
"limits": [
{
"counter": "import_markdown_folder_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} import_markdown_folder stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Import all markdown files from a folder. 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 import_markdown_folder: 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.
import_markdown_folder 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 import_markdown_folder 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 import_markdown_folder. 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.
import_markdown_folder is provided by the Obsidian MCP Server MCP server (kynlos/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
120 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.