# context_health

One-call memory checkup: store size, memory counts by kind (semantic/episodic/procedural), engine

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

## Facts

- Tool: `context_health`
- 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: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why context_health is rated Low

This tool exclusively retrieves and reports diagnostic metadata about the memory system's health and composition. No data is created, modified, deleted, or executed. It is a passive inspection mechanism analogous to a system status query, which is characteristic of the Read category.

From the tool's own definition: "Tool description indicates it performs a 'checkup' reporting on 'store size, memory counts by kind, engine' — these are diagnostic read operations that retrieve and report on memory system metrics without modifying data."

## Use case

AI agents call context_health to retrieve information from Chitta without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "context_health": {}
  }
}
```

## 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_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
- `context_ingest` — Write — https://policylayer.com/tools/100xprompt-chitta/context-ingest.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