context_relate

Query the knowledge graph AS A GRAPH (not text search). Four modes:\n

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

WHAT IT DOES

What context_relate does on Chitta

AI agents call context_relate 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_relate is rated Low

This tool retrieves and explores data structures (knowledge graph relationships) without modifying, deleting, or executing external operations. It has no side effects beyond read access. The permission-aware architecture and per-user access control further support that this is a controlled read operation.

From the tool's definition Tool queries 'the knowledge graph AS A GRAPH' to retrieve relationships and data. The description emphasizes querying/retrieval functionality with 'four modes' that appear to be different graph traversal or relationship-finding operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs context_relate 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_relate, this is the rule to start with:

context_relate Allowed

context_relate 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_relate": {}
  }
}

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_relate call is checked against it from then on.

FAQ

Questions about context_relate

What does the context_relate tool do? +

Query the knowledge graph AS A GRAPH (not text search). Four modes:\n. 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_relate? +

Register the Chitta MCP server in PolicyLayer and add a rule for context_relate: 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_relate? +

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

Can I rate-limit context_relate? +

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

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

context_relate 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 →