# search_entities

A read tool on the Optimized Memory MCP Server V2 MCP server.

Agent View of the PolicyLayer registry record for `search_entities`. HTML page: https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/search-entities

## Facts

- Tool: `search_entities`
- Server: Optimized Memory MCP Server V2 (`agentwong/optimized-memory-mcp-serverv2`) — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2.md
- Homepage: https://github.com/AgentWong/optimized-memory-mcp-serverv2
- 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_entities",
    "arguments": {}
  }
}
```

## Why search_entities is rated Low

Search operations are read-only queries that retrieve or filter existing data without side effects. Given the context of a memory management server with sibling tools like 'create_entity', 'delete_entity', 'analyze_provider', the 'search_entities' tool fits the pattern of a retrieval function.

From the tool's own definition: "Tool name 'search_entities' indicates a query operation that retrieves entities. The suffix 'search_' is characteristic of Read operations that query data without modification. The description is empty, but the name itself strongly suggests data retrieval."

## Use case

AI agents call search_entities to retrieve information from Optimized Memory MCP Server V2 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 Optimized Memory MCP Server V2:

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

## Other tools on Optimized Memory MCP Server V2 (16)

- `delete_entity` — Destructive — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/delete-entity.md
- `delete_observation` — Destructive — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/delete-observation.md
- `delete_relationship` — Destructive — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/delete-relationship.md
- `async_tool` — Other — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/async-tool.md
- `my_tool` — Other — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/my-tool.md
- `tool_with_context` — Other — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/tool-with-context.md
- `analyze_provider` — Read — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/analyze-provider.md
- `add_version` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/add-version.md
- `create_entity` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/create-entity.md
- `create_observation` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/create-observation.md
- `create_relationship` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/create-relationship.md
- `register_collection` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/register-collection.md
- `register_provider` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/register-provider.md
- `update_entity` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/update-entity.md
- `update_observation` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/update-observation.md
- `update_relationship` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/update-relationship.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=agentwong-optimized-memory-mcp-serverv2 · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/agentwong-optimized-memory-mcp-serverv2