New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

clear_expired_context_cache

Clear expired documentation cache entries.

SERVERObsidian Elite RAG MCP Server SOURCEaegntic/aegntic-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about clear_expired_context_cache

What does the clear_expired_context_cache tool do? +

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.

How do I enforce a policy on clear_expired_context_cache? +

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.

What risk level is clear_expired_context_cache? +

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.

Can I rate-limit clear_expired_context_cache? +

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.

How do I block clear_expired_context_cache completely? +

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.

What MCP server provides clear_expired_context_cache? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Obsidian Elite RAG MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.