clear_working_memory

THE RISK

Critical Risk

This tool irreversibly removes/clears working memory entries from the local store. The word 'clear' implies bulk deletion of stored data. While these are generated/cached entries rather than source code, clearing them destroys stored intelligence context that may not be easily recoverable, making it Destructive rather than Write.

From the tool's definition "Clear generated working memory entries from the local managed store"

Documented attack patterns abuse exactly the kind of access clear_working_memory gives an agent:

HOW TO CONTROL CLEAR_WORKING_MEMORY

PolicyLayer is an MCP gateway — it sits between your AI agents and Reporecall, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_working_memory:

policy.json

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

clear_working_memory disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Reporecall — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Reporecall tools

Destructive clear_index Clear all indexed data Destructive forget_memory Delete a memory by name. Removes the file and its index entries. Execute index_codebase Index or re-index the codebase. Also regenerates deterministic wiki/business pages when th Write compact_memories Refresh and compact memory indexes. Falls back to a safe refresh if the compactor is not a Write store_memory Create or update a memory file. The memory will be indexed for future recall. Write wiki_write Create or update a wiki page manually. Use this to persist codebase knowledge that should Read build_stack_tree Build a bidirectional call tree from a seed function/method. Shows callers (who invokes it Read business_context_query Find product areas and business capability pages relevant to a query. Returns business-fac

All 30 Reporecall tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Reporecall → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the clear_working_memory tool do? +

Clear generated working memory entries from the local managed store. It is categorised as a Destructive tool in the Reporecall 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_working_memory? +

Register the Reporecall MCP server in PolicyLayer and add a rule for clear_working_memory: 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 Reporecall. Nothing to install.

What risk level is clear_working_memory? +

clear_working_memory 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_working_memory? +

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

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

clear_working_memory is provided by the Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Reporecall tool call.

Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN REPORECALL →

Free to start. No card required.

30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT CLEAR_WORKING_MEMORY ON REPORECALL DOES

// THE RISK

// HOW TO CONTROL CLEAR_WORKING_MEMORY

// EXPLORE