remove_concept

Soft-delete a concept from the knowledge graph. The concept and its removal reason are preserved in history.

SERVERMegaMemory SOURCE0xk3vin/megamemory

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/0xk3vin-megamemory/remove-concept.md

WHAT IT DOES

What remove_concept does on MegaMemory

AI agents call remove_concept to permanently remove resources in MegaMemory, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_concept is rated Critical

This tool modifies the accessible state of the knowledge graph in an irreversible manner (within the active graph scope). Even though historical preservation exists, the concept is deleted from active use—an agent cannot recover it for ongoing reasoning without explicit recovery actions.

From the tool's definition Tool name 'remove_concept' and description 'Soft-delete a concept from the knowledge graph' indicates deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_concept safely

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

remove_concept Hidden

remove_concept 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": [
    "remove_concept"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MegaMemory, apply this rule, and every remove_concept call is checked against it from then on.

FAQ

Questions about remove_concept

What does the remove_concept tool do? +

Soft-delete a concept from the knowledge graph. The concept and its removal reason are preserved in history. It is categorised as a Destructive tool in the MegaMemory 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 remove_concept? +

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

What risk level is remove_concept? +

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

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

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

remove_concept is provided by the MegaMemory MCP server (0xk3vin/megamemory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MegaMemory, and thousands of servers like it.

This server

All 9 MegaMemory tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →