context_profile

Get a synthesized profile of a person, org, or any entity - the permanent facts, the most recent facts,

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

WHAT IT DOES

What context_profile does on Chitta

AI agents call context_profile 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_profile is rated Low

This tool retrieves and queries synthesized profile information from the knowledge graph without modifying, deleting, or executing operations. However, severity is rated 'medium' rather than 'low' because profiles of persons/orgs could contain sensitive personal or organizational information that, if accessed inappropriately by an agent, could enable privacy violations, targeted attacks, or social engineering.

From the tool's definition Tool name 'context_profile' and description 'Get a synthesized profile of a person, org, or any entity - the permanent facts, the most recent facts' indicate data retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

context_profile Allowed

context_profile 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_profile": {}
  }
}

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

FAQ

Questions about context_profile

What does the context_profile tool do? +

Get a synthesized profile of a person, org, or any entity - the permanent facts, the most recent facts,. 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_profile? +

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

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

Can I rate-limit context_profile? +

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

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

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