forget_memory
Remove saved memories matching a description. Call this when the user says to forget or stop applying
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/forget-memory.md
What forget_memory does on Samarth Gtm Mcp
AI agents call forget_memory to permanently remove resources in Samarth Gtm Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why forget_memory is rated Critical
Irreversibly deletes stored data without undo capability. Medium severity due to limited scope to cached memories.
From the tool's definition Remove saved memories matching a description. Call this when the user says to forget
Attacks that exploit this kind of access
The rule that runs forget_memory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For forget_memory, this is the rule to start with:
forget_memory 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 Samarth Gtm Mcp, apply this rule, and every forget_memory call is checked against it from then on.
Questions about forget_memory
Remove saved memories matching a description. Call this when the user says to forget or stop applying. It is categorised as a Destructive tool in the Samarth Gtm Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for forget_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 Samarth Gtm Mcp. Nothing to install.
forget_memory 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 forget_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.
Set action: deny in the PolicyLayer policy for forget_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.
forget_memory is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Samarth Gtm, and thousands of servers like it.
Across the catalogue