context_about
Describe this context server: its purpose, current mode/identity/storage, the vector + knowledge-graph
This record as markdown: /tools/100xprompt-chitta/context-about.md
What context_about does on Chitta
AI agents call context_about 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.
Why context_about is rated Low
This is a descriptive/informational query that retrieves server metadata and status. It has no side effects—it cannot create, modify, delete, or execute operations. The blast radius of misuse is minimal; an AI agent learning about the server's architecture poses no direct risk to data integrity or availability. Classified as Read with low severity.
From the tool's definition Tool name 'context_about' and description 'Describe this context server' indicate retrieval and introspection of metadata about the server's configuration, purpose, and internal state (vector + knowledge-graph structure).
Attacks that exploit this kind of access
The rule that runs context_about 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_about, this is the rule to start with:
context_about is read-only, so it stays allowed. 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_about call is checked against it from then on.
Questions about context_about
Describe this context server: its purpose, current mode/identity/storage, the vector + knowledge-graph. It is categorised as a Read tool in the Chitta MCP Server, which means it retrieves data without modifying state.
Register the Chitta MCP server in PolicyLayer and add a rule for context_about: 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_about is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the context_about 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_about. 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_about 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.
This server
Across the catalogue