# search_recent

A read tool on the MyChatArchive MCP Server MCP server.

Agent View of the PolicyLayer registry record for `search_recent`. HTML page: https://policylayer.com/tools/1ch1n-mychatarchive/search-recent

## Facts

- Tool: `search_recent`
- 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": "search_recent",
    "arguments": {}
  }
}
```

## Why search_recent is rated Low

Based on the server's stated purpose of enabling search and retrieval across conversation history, 'search_recent' most likely retrieves recent conversation data without modifying it. The absence of a tool description lowers confidence slightly, but the naming convention and server context strongly indicate a Read operation with no side effects or data modification capabilities.

From the tool's own definition: "Tool name 'search_recent' and server description indicating 'semantic search across your local AI conversation history' and 'retrieve context' suggest a query/retrieval operation. No description provided for the specific tool."

## Use case

AI agents call search_recent 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": {
    "search_recent": {}
  }
}
```

## Other tools on MyChatArchive MCP Server (5)

- `get_context` — Read — https://policylayer.com/tools/1ch1n-mychatarchive/get-context.md
- `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
- `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