# get_context

A read tool on the MyChatArchive MCP Server MCP server.

Agent View of the PolicyLayer registry record for `get_context`. HTML page: https://policylayer.com/tools/1ch1n-mychatarchive/get-context

## Facts

- Tool: `get_context`
- Server: MyChatArchive MCP Server (`1ch1n/mychatarchive`) — https://policylayer.com/tools/1ch1n-mychatarchive.md
- Homepage: https://github.com/1ch1n/mychatarchive
- Risk category: Read (Low risk)
- Registry record: grade A, 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": "get_context",
    "arguments": {}
  }
}
```

## Why get_context is rated Low

The tool appears to retrieve contextual information from stored conversation data without modifying, executing operations, or causing destructive effects. This is consistent with a Read category operation. Confidence is moderate (0.75) rather than high because the tool description is empty, leaving some ambiguity about exact functionality. If it permits arbitrary code execution or writing, severity would be higher.

From the tool's own definition: "Tool name 'get_context' with sibling tools including 'search_brain', 'search_recent', and 'capture_thought' indicates this is part of a retrieval system. Server description states it 'retrieves context' from local conversation history."

## Use case

AI agents call get_context to retrieve information from MyChatArchive MCP Server 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 MyChatArchive MCP Server:

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

## Other tools on MyChatArchive MCP Server (5)

- `get_current_datetime` — Read — https://policylayer.com/tools/1ch1n-mychatarchive/get-current-datetime.md
- `get_profile` — Read — https://policylayer.com/tools/1ch1n-mychatarchive/get-profile.md
- `search_brain` — Read — https://policylayer.com/tools/1ch1n-mychatarchive/search-brain.md
- `search_recent` — Read — https://policylayer.com/tools/1ch1n-mychatarchive/search-recent.md
- `capture_thought` — Write — https://policylayer.com/tools/1ch1n-mychatarchive/capture-thought.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=1ch1n-mychatarchive · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1ch1n-mychatarchive