context_rebuild
Re-extract the knowledge graph over ALL stored records using the current extractor, then rebuild the
This record as markdown: /tools/100xprompt-chitta/context-rebuild.md
What context_rebuild does on Chitta
AI agents invoke context_rebuild to trigger actions in Chitta. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why context_rebuild is rated High
This tool triggers a large-scale re-processing operation over ALL stored records, rebuilding the entire knowledge graph. It is not a simple read or write — it executes a bulk extraction and reconstruction pipeline. Misuse could overwrite or corrupt the entire knowledge graph, cause significant resource consumption, or produce incorrect graph state.
From the tool's definition Re-extract the knowledge graph over ALL stored records using the current extractor, then rebuild the
Attacks that exploit this kind of access
The rule that runs context_rebuild 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_rebuild, this is the rule to start with:
context_rebuild stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chitta, apply this rule, and every context_rebuild call is checked against it from then on.
Questions about context_rebuild
Re-extract the knowledge graph over ALL stored records using the current extractor, then rebuild the. It is categorised as a Execute tool in the Chitta MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chitta MCP server in PolicyLayer and add a rule for context_rebuild: 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.
context_rebuild is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the context_rebuild 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.
Set action: deny in the PolicyLayer policy for context_rebuild. 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.
context_rebuild 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.
More on Chitta, and thousands of servers like it.
Across the catalogue