context_forget
Forget stored memories that are no longer true or wanted. USE WHEN: the user says
This record as markdown: /tools/100xprompt-chitta/context-forget.md
What context_forget does on Chitta
AI agents call context_forget to permanently remove resources in Chitta, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why context_forget is rated Critical
Forgetting memories implies irreversible deletion of stored data from the knowledge graph and vector memory. There is no indication of a recovery or undo mechanism. Misuse by an AI agent could cause permanent loss of user context, knowledge, or memory entries, making this Destructive with high severity.
From the tool's definition 'Forget stored memories that are no longer true or wanted' — permanently removes stored memory entries from the knowledge-graph/vector memory store
Attacks that exploit this kind of access
The rule that runs context_forget safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chitta, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For context_forget, this is the rule to start with:
context_forget 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 Chitta, apply this rule, and every context_forget call is checked against it from then on.
Questions about context_forget
Forget stored memories that are no longer true or wanted. USE WHEN: the user says. It is categorised as a Destructive tool in the Chitta MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Chitta MCP server in PolicyLayer and add a rule for context_forget: 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 Chitta. Nothing to install.
context_forget 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 context_forget 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 context_forget. 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.
context_forget is provided by the Chitta MCP server (@100xprompt/chitta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chitta, and thousands of servers like it.
Across the catalogue