get_context
Recall stored knowledge. USE WHEN: answering anything that could touch the user
This record as markdown: /tools/100xprompt-chitta/get-context.md
What get_context does on Chitta
AI agents call get_context 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 get_context is rated Low
This tool retrieves pre-stored knowledge from the memory system without modifying data or executing external operations. It is purely a read operation that queries the knowledge graph or vector memory. The severity is low because retrieval alone poses minimal risk; misuse would expose existing data rather than destroy, modify, or execute arbitrary code.
From the tool's definition Tool name 'get_context' and description 'Recall stored knowledge' indicate a retrieval operation. The phrase 'could touch the user' suggests data access rather than modification. No creation, deletion, or external execution capabilities are evident.
Attacks that exploit this kind of access
The rule that runs get_context 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 get_context, this is the rule to start with:
get_context 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 get_context call is checked against it from then on.
Questions about get_context
Recall stored knowledge. USE WHEN: answering anything that could touch the user. 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 get_context: 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.
get_context 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 get_context 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 get_context. 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.
get_context 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