Get recently modified files in the vault.
AI agents call get_recent_changes to retrieve information from Obsidian Modified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists recently modified files, which is a read-only operation with no side effects. It does not create, modify, delete, execute, or initiate any changes to the vault data. The low severity reflects minimal blast radius—the only risk would be information disclosure of vault structure/activity, which is non-destructive and typical for a personal note-taking tool.
From the tool's definition Tool name 'get_recent_changes' and description 'Get recently modified files in the vault' indicate a query operation that retrieves metadata about file modification history with no modification or deletion of vault contents.
Attacks that exploit this kind of access
Get recently modified files in the vault. It is categorised as a Read tool in the Obsidian Modified MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Modified MCP server in PolicyLayer and add a rule for get_recent_changes: 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 Modified. Nothing to install.
get_recent_changes 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 get_recent_changes 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 get_recent_changes. 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.
get_recent_changes is provided by the Obsidian Modified MCP server (@marwansaab/obsidian-modified-mcp-server). 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 →