# search_memory

Search memories using semantic similarity. Use default (detailed=false) for quick exploration or when context is sufficient; it shows previews with IDs and saves input tokens. Use detailed=true only when you need the full text of results. For a specific item, use get_memory(id) after getting the ID from search. TIP: Filter by project to avoid mixing contexts from different workspaces.

Agent View of the PolicyLayer registry record for `search_memory`. HTML page: https://policylayer.com/tools/0xrelogic-cognio/search-memory

## Facts

- Tool: `search_memory`
- Server: Cognio (`0xrelogic/cognio`) — https://policylayer.com/tools/0xrelogic-cognio.md
- Homepage: https://github.com/0xReLogic/Cognio
- Risk category: Read (Low risk)
- Registry record: grade D, 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_memory",
    "arguments": {}
  }
}
```

## Why search_memory is rated Low

This is a query/search operation that retrieves and examines stored data without side effects. The tool returns memory previews or full text based on parameters, but does not create, modify, delete, or execute any operations. Even with detailed=true, it only increases verbosity of read results. Severity is low because unauthorized memory search poses informational risk but limited operational danger in isolation.

From the tool's own definition: "Tool performs 'search memories using semantic similarity' with options for preview or detailed viewing. Description explicitly contrasts with get_memory(id) for retrieval and recommends filtering by project."

## Use case

AI agents call search_memory to retrieve information from Cognio 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 Cognio:

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

## Other tools on Cognio (11)

- `delete_memory` — Destructive — https://policylayer.com/tools/0xrelogic-cognio/delete-memory.md
- `export_memories` — Read — https://policylayer.com/tools/0xrelogic-cognio/export-memories.md
- `get_active_project` — Read — https://policylayer.com/tools/0xrelogic-cognio/get-active-project.md
- `get_memory` — Read — https://policylayer.com/tools/0xrelogic-cognio/get-memory.md
- `get_memory_stats` — Read — https://policylayer.com/tools/0xrelogic-cognio/get-memory-stats.md
- `list_memories` — Read — https://policylayer.com/tools/0xrelogic-cognio/list-memories.md
- `list_projects` — Read — https://policylayer.com/tools/0xrelogic-cognio/list-projects.md
- `summarize_text` — Read — https://policylayer.com/tools/0xrelogic-cognio/summarize-text.md
- `archive_memory` — Write — https://policylayer.com/tools/0xrelogic-cognio/archive-memory.md
- `save_memory` — Write — https://policylayer.com/tools/0xrelogic-cognio/save-memory.md
- `set_active_project` — Write — https://policylayer.com/tools/0xrelogic-cognio/set-active-project.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=0xrelogic-cognio · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xrelogic-cognio