# search_similar

Search for similar entities and relations using semantic search

Agent View of the PolicyLayer registry record for `search_similar`. HTML page: https://policylayer.com/tools/delorenj-mcp-qdrant-memory/search-similar

## Facts

- Tool: `search_similar`
- Server: MCP Memory Server with Qdrant Persistence (`delorenj/mcp-qdrant-memory`) — https://policylayer.com/tools/delorenj-mcp-qdrant-memory.md
- Homepage: https://github.com/delorenj/mcp-qdrant-memory
- Risk category: Read (Low risk)
- Registry record: grade F, 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_similar",
    "arguments": {}
  }
}
```

## Why search_similar is rated Low

This is a retrieval operation that queries existing data in the knowledge graph without side effects. Semantic search is a read-only operation that returns results based on similarity metrics. The tool does not create, modify, delete, or execute arbitrary operations—it only searches and returns matching entities and relations.

From the tool's own definition: "Tool name 'search_similar' and description 'Search for similar entities and relations using semantic search' indicate a query operation that retrieves data via semantic similarity matching against a Qdrant vector database."

## Use case

AI agents call search_similar to retrieve information from MCP Memory Server with Qdrant Persistence 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 MCP Memory Server with Qdrant Persistence:

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

## Other tools on MCP Memory Server with Qdrant Persistence (7)

- `delete_entities` — Destructive — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/delete-entities.md
- `delete_observations` — Destructive — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/delete-observations.md
- `delete_relations` — Destructive — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/delete-relations.md
- `read_graph` — Read — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/read-graph.md
- `add_observations` — Write — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/add-observations.md
- `create_entities` — Write — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/create-entities.md
- `create_relations` — Write — https://policylayer.com/tools/delorenj-mcp-qdrant-memory/create-relations.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=delorenj-mcp-qdrant-memory · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/delorenj-mcp-qdrant-memory