# context_profile

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

Agent View of the PolicyLayer registry record for `context_profile`. HTML page: https://policylayer.com/tools/100xprompt-chitta/context-profile

## Facts

- Tool: `context_profile`
- Server: Chitta (`@100xprompt/chitta`) — https://policylayer.com/tools/100xprompt-chitta.md
- Install: `npx -y @100xprompt/chitta`
- Homepage: https://www.npmjs.com/package/@100xprompt/chitta
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "context_profile",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Chitta:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "context_profile": {}
  }
}
```

## Other tools on Chitta (10)

- `context_forget` — Destructive — https://policylayer.com/tools/100xprompt-chitta/context-forget.md
- `context_rebuild` — Execute — https://policylayer.com/tools/100xprompt-chitta/context-rebuild.md
- `context_about` — Read — https://policylayer.com/tools/100xprompt-chitta/context-about.md
- `context_graph` — Read — https://policylayer.com/tools/100xprompt-chitta/context-graph.md
- `context_health` — Read — https://policylayer.com/tools/100xprompt-chitta/context-health.md
- `context_reflect` — Read — https://policylayer.com/tools/100xprompt-chitta/context-reflect.md
- `context_relate` — Read — https://policylayer.com/tools/100xprompt-chitta/context-relate.md
- `context_timeline` — Read — https://policylayer.com/tools/100xprompt-chitta/context-timeline.md
- `get_context` — Read — https://policylayer.com/tools/100xprompt-chitta/get-context.md
- `context_ingest` — Write — https://policylayer.com/tools/100xprompt-chitta/context-ingest.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=100xprompt-chitta · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/100xprompt-chitta