AI agents call vault_timeline to retrieve information from Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves temporal metadata (creation and modification timestamps) about notes in the vault. It performs a read-only query operation with no side effects, no data modification, and no execution of arbitrary code. The information retrieved is non-sensitive vault metadata that does not enable destructive, financial, or write operations.
From the tool's definition Tool name 'vault_timeline' and description 'Get creation/modification timeline of notes' indicate retrieval of metadata without modification or deletion.
Documented attack patterns abuse exactly the kind of access vault_timeline 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 vault_timeline:
{
"version": "1",
"default": "deny",
"tools": {
"vault_timeline": {}
}
}vault_timeline is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get creation/modification timeline of notes. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for vault_timeline: 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.
vault_timeline 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 vault_timeline 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 vault_timeline. 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.
vault_timeline 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.