Export notes in various formats. Supports single notes, hub + children consolidated, or directories. Formats: - markdown: Wiki-links intact, original format - clean_markdown: Wiki-links converted to plain text - resolved_markdown: Wiki-links converted to relative markdown links - html: Rendered H...
AI agents call palace_export to retrieve information from Obsidian Palace MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The primary function is reading/retrieving notes from the Obsidian vault and rendering them in various formats. However, 'Can write to file' indicates a potential Write side effect when exporting to disk. The dominant action is retrieval/export of existing data, but the file-write capability slightly elevates severity.
From the tool's definition Export notes in various formats... Can write to file or return content
Attacks that exploit this kind of access
Export notes in various formats. Supports single notes, hub + children consolidated, or directories. Formats: - markdown: Wiki-links intact, original format - clean_markdown: Wiki-links converted to plain text - resolved_markdown: Wiki-links converted to relative markdown links - html: Rendered HTML with optional styling Features: - Automatically consolidates hub notes with their children - Handles nested hub structures recursively - Optional frontmatter inclusion or conversion to header - Can write to file or return content. It is categorised as a Read tool in the Obsidian Palace MCP MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_export: 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 Palace MCP. Nothing to install.
palace_export is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the palace_export 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 palace_export. 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.
palace_export is provided by the Obsidian Palace MCP server (probably-computers/obsidian-palace-mcp). 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 →