# create_concept

Add a new concept to the knowledge graph. Call this after completing a task to record new features, components, patterns, or decisions you built. Include specific details: parameter names, defaults, file locations, and rationale.

Agent View of the PolicyLayer registry record for `create_concept`. HTML page: https://policylayer.com/tools/0xk3vin-megamemory/create-concept

## Facts

- Tool: `create_concept`
- Server: MegaMemory (`0xk3vin/megamemory`) — https://policylayer.com/tools/0xk3vin-megamemory.md
- Homepage: https://github.com/0xK3vin/MegaMemory
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_concept",
    "arguments": {}
  }
}
```

## Why create_concept is rated Medium

This tool creates new data entries in a persistent knowledge graph, which is a Write operation. It is reversible (concepts can be removed via remove_concept sibling tool).

From the tool's own definition: "Tool description explicitly states 'Add a new concept to the knowledge graph' and instructs to 'record new features, components, patterns, or decisions.' This creates and adds data reversibly to a persistent knowledge structure."

## Use case

AI agents use create_concept to create or update resources in MegaMemory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MegaMemory environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MegaMemory:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_concept": {
      "limits": [
        {
          "counter": "create_concept_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on MegaMemory (8)

- `remove_concept` — Destructive — https://policylayer.com/tools/0xk3vin-megamemory/remove-concept.md
- `get_concept` — Read — https://policylayer.com/tools/0xk3vin-megamemory/get-concept.md
- `list_conflicts` — Read — https://policylayer.com/tools/0xk3vin-megamemory/list-conflicts.md
- `list_roots` — Read — https://policylayer.com/tools/0xk3vin-megamemory/list-roots.md
- `understand` — Read — https://policylayer.com/tools/0xk3vin-megamemory/understand.md
- `link` — Write — https://policylayer.com/tools/0xk3vin-megamemory/link.md
- `resolve_conflict` — Write — https://policylayer.com/tools/0xk3vin-megamemory/resolve-conflict.md
- `update_concept` — Write — https://policylayer.com/tools/0xk3vin-megamemory/update-concept.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xk3vin-megamemory · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xk3vin-megamemory