context_health

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

SERVERChitta SOURCE@100xprompt/chitta

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/100xprompt-chitta/context-health.md

WHAT IT DOES

What context_health does on Chitta

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.

RISK

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 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs context_health safely

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

context_health Allowed

context_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about context_health

What does the context_health tool do? +

One-call memory checkup: store size, memory counts by kind (semantic/episodic/procedural), engine. It is categorised as a Read tool in the Chitta MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on context_health? +

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

What risk level is context_health? +

context_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit context_health? +

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

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

context_health is provided by the Chitta MCP server (@100xprompt/chitta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chitta, and thousands of servers like it.

This server

All 11 Chitta tools →

Across the catalogue

editor_context on 010 Editor →search_context on ACE-MCP → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →