# context_ingest

Remember new information durably. USE WHEN: the user states a fact, preference, person, project,

Agent View of the PolicyLayer registry record for `context_ingest`. HTML page: https://policylayer.com/tools/100xprompt-chitta/context-ingest

## Facts

- Tool: `context_ingest`
- Server: Chitta (`@100xprompt/chitta`) — https://policylayer.com/tools/100xprompt-chitta.md
- Install: `npx -y @100xprompt/chitta`
- Homepage: https://www.npmjs.com/package/@100xprompt/chitta
- Risk category: Write (Medium risk)
- Registry record: grade B, 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": "context_ingest",
    "arguments": {}
  }
}
```

## Why context_ingest is rated Medium

This tool ingests and durably stores new information into the memory system, which is a write/create operation. It is reversible (there is a sibling 'context_forget' tool suggesting deletion is possible), so it falls under Write rather than Destructive. Medium severity because an AI agent could store false, sensitive, or manipulated information into persistent memory, affecting future agent behavior.

From the tool's own definition: "'Remember new information durably' — creates/stores new data persistently in the knowledge-graph + vector memory"

## Use case

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

## Recommended policy (PolicyLayer)

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

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

## Other tools on Chitta (10)

- `context_forget` — Destructive — https://policylayer.com/tools/100xprompt-chitta/context-forget.md
- `context_rebuild` — Execute — https://policylayer.com/tools/100xprompt-chitta/context-rebuild.md
- `context_about` — Read — https://policylayer.com/tools/100xprompt-chitta/context-about.md
- `context_graph` — Read — https://policylayer.com/tools/100xprompt-chitta/context-graph.md
- `context_health` — Read — https://policylayer.com/tools/100xprompt-chitta/context-health.md
- `context_profile` — Read — https://policylayer.com/tools/100xprompt-chitta/context-profile.md
- `context_reflect` — Read — https://policylayer.com/tools/100xprompt-chitta/context-reflect.md
- `context_relate` — Read — https://policylayer.com/tools/100xprompt-chitta/context-relate.md
- `context_timeline` — Read — https://policylayer.com/tools/100xprompt-chitta/context-timeline.md
- `get_context` — Read — https://policylayer.com/tools/100xprompt-chitta/get-context.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=100xprompt-chitta · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/100xprompt-chitta