clear_expired_context_cache
Clear expired documentation cache entries.
This record as markdown: /tools/aegntic-aegntic-mcp/clear-expired-context-cache.md
What clear_expired_context_cache does on Obsidian Elite RAG MCP Server
AI agents call clear_expired_context_cache to permanently remove resources in Obsidian Elite RAG MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear_expired_context_cache is rated Critical
Clearing cache entries is an irreversible deletion operation; once cache entries are removed they cannot be restored without re-indexing/re-processing. While 'expired' entries are targeted (suggesting lower blast radius than a full cache wipe), the action is still a deletion that cannot be undone, placing it in the Destructive category.
From the tool's definition 'Clear expired documentation cache entries' — the action permanently removes cache entries
Attacks that exploit this kind of access
The rule that runs clear_expired_context_cache safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian Elite RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_expired_context_cache, this is the rule to start with:
clear_expired_context_cache is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian Elite RAG MCP Server, apply this rule, and every clear_expired_context_cache call is checked against it from then on.
Questions about clear_expired_context_cache
Clear expired documentation cache entries. It is categorised as a Destructive tool in the Obsidian Elite RAG MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian Elite RAG MCP Server MCP server in PolicyLayer and add a rule for clear_expired_context_cache: 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 Elite RAG MCP Server. Nothing to install.
clear_expired_context_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_expired_context_cache 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 clear_expired_context_cache. 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.
clear_expired_context_cache is provided by the Obsidian Elite RAG MCP Server MCP server (aegntic/aegntic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian Elite RAG MCP Server, and thousands of servers like it.
Across the catalogue