get_context

A read tool on the MyChatArchive MCP server.

SERVERMyChatArchive MCP Server SOURCE1ch1n/mychatarchive

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/1ch1n-mychatarchive/get-context.md

WHAT IT DOES

What get_context does on MyChatArchive MCP Server

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.

RISK

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MyChatArchive MCP Server, 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 Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MyChatArchive MCP Server, apply this rule, and every get_context call is checked against it from then on.

FAQ

Questions about get_context

What does the get_context tool do? +

get_context is a read tool on the MyChatArchive MCP Server MCP server. It is categorised as a Read tool in the MyChatArchive MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_context? +

Register the MyChatArchive MCP Server 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 MyChatArchive MCP Server. Nothing to install.

What risk level is get_context? +

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

Can I rate-limit get_context? +

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.

How do I block get_context completely? +

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.

What MCP server provides get_context? +

get_context is provided by the MyChatArchive MCP Server MCP server (1ch1n/mychatarchive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MyChatArchive MCP Server, and thousands of servers like it.

This server

All 6 MyChatArchive MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →editor_context on 010 Editor →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →