AI agents use export_to_pdf 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.
Export operations create new files and thus involve write operations. However, the severity is low because: (1) the action is reversible (exported PDFs can be deleted), (2) it has no side effects on the vault itself or other data, (3) it requires the markdown-pdf dependency which is a standard tool, and (4) the blast radius of misuse is minimal—an agent could create unwanted PDF files but cannot corrupt, delete, or…
From the tool's definition Tool description states it 'Export a note as PDF', which creates a new output file/document based on an existing note. This is a write operation that generates new data (a PDF file) without modifying the source note or deleting data.
Documented attack patterns abuse exactly the kind of access export_to_pdf 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 export_to_pdf:
{
"version": "1",
"default": "deny",
"tools": {
"export_to_pdf": {
"limits": [
{
"counter": "export_to_pdf_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_to_pdf 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.
Export a note as PDF (requires markdown-pdf). 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 export_to_pdf: 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.
export_to_pdf 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 export_to_pdf 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 export_to_pdf. 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.
export_to_pdf 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.