cache_clear

v12.5.0 \u2014 Bust all four global search caches. Idempotent; safe after manual graph edits to drop stale results.

SERVEREnhanced Knowledge Graph Memory Server SOURCEdanielsimonjr/memory-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/danielsimonjr-memory-mcp/cache-clear.md

WHAT IT DOES

What cache_clear does on Enhanced Knowledge Graph Memory Server

AI agents call cache_clear to permanently remove resources in Enhanced Knowledge Graph Memory Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cache_clear is rated Critical

An AI agent that decides to call cache_clear doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Enhanced Knowledge Graph Memory Server is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cache_clear safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cache_clear, this is the rule to start with:

cache_clear Hidden

cache_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cache_clear"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every cache_clear call is checked against it from then on.

FAQ

Questions about cache_clear

What does the cache_clear tool do? +

v12.5.0 \u2014 Bust all four global search caches. Idempotent; safe after manual graph edits to drop stale results. It is categorised as a Destructive tool in the Enhanced Knowledge Graph Memory 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 cache_clear? +

Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for cache_clear: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.

What risk level is cache_clear? +

cache_clear 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 cache_clear? +

Yes. Add a rate_limit block to the cache_clear 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 cache_clear completely? +

Set action: deny in the PolicyLayer policy for cache_clear. 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 cache_clear? +

cache_clear is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.

This server

All 225 Enhanced Knowledge Graph Memory Server tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →