View version history for a note. Shows timestamps, operations, and optionally diffs between versions. Use compare to diff two specific versions.
AI agents call palace_history 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.
palace_history retrieves and displays version control information about notes—a non-destructive, non-side-effect operation. It queries existing historical metadata and comparison data without creating, modifying, deleting, or executing anything. The 'compare' feature for diffing is also a read operation. This is a classic information retrieval tool with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states 'View version history' and 'Shows timestamps, operations, and optionally diffs between versions.' The verb 'View' and 'Shows' indicate read-only retrieval of historical data without modification or execution.
Attacks that exploit this kind of access
View version history for a note. Shows timestamps, operations, and optionally diffs between versions. Use compare to diff two specific versions. 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_history: 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_history 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_history 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_history. 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_history 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 →