remove_concept

THE RISK

Critical Risk

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.

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

HOW TO CONTROL REMOVE_CONCEPT

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

policy.json

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

remove_concept 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 MegaMemory — 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 MegaMemory tools

Write create_concept Add a new concept to the knowledge graph. Call this after completing a task to record new Write link Create a relationship between two existing concepts. Write resolve_conflict Resolve a merge conflict by providing the correct resolved content. Read both conflict ver Write update_concept Update an existing concept in the knowledge graph. Call this after completing a task that Read get_concept Look up a concept by its exact ID. Returns the concept with its full context including chi Read list_conflicts List all unresolved merge conflicts in the knowledge graph, grouped by merge_group. Each g Read list_roots List all top-level concepts in the knowledge graph with their direct children. Call this a Read understand Query the project knowledge graph. Call this before starting any task to load relevant con

All 9 MegaMemory tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan Frida Agent MCP kill_app 1MCP Server mcp_uninstall Code delete_path

Go deeper

Critical-risk tools in MegaMemory → 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 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.

Enforce policy on every MegaMemory tool call.

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

GOVERN MEGAMEMORY →

Free to start. No card required.

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

// WHAT REMOVE_CONCEPT ON MEGAMEMORY DOES

// THE RISK

// HOW TO CONTROL REMOVE_CONCEPT

// EXPLORE