# find_related

A read tool on the Agent Store MCP server.

Agent View of the PolicyLayer registry record for `find_related`. HTML page: https://policylayer.com/tools/agent-store/find-related

## Facts

- Tool: `find_related`
- Server: Agent Store (`chrisluersen/agent-store`) — https://policylayer.com/tools/agent-store.md
- Homepage: https://github.com/chrisluersen/agent-store
- 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": "find_related",
    "arguments": {}
  }
}
```

## Why find_related is rated Low

The name 'find_related' most naturally implies a search or lookup operation that retrieves associated data without modifying state. This aligns with the Read category. However, the empty description and lack of parameter details create uncertainty. The sibling tools (gbrain_search, gbrain_query, gbrain_get_page, gbrain_list_pages) are all Read operations, suggesting this server is query-focused.

From the tool's own definition: "Tool name 'find_related' suggests retrieval or query of related items; description is empty, limiting confidence in classification."

## Use case

AI agents call find_related to retrieve information from Agent Store 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 Agent Store:

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

## Other tools on Agent Store (18)

- `fleet_dispatch` — Execute — https://policylayer.com/tools/agent-store/fleet-dispatch.md
- `gbrain_query` — Execute — https://policylayer.com/tools/agent-store/gbrain-query.md
- `gbrain_think` — Execute — https://policylayer.com/tools/agent-store/gbrain-think.md
- `reindex_wiki` — Execute — https://policylayer.com/tools/agent-store/reindex-wiki.md
- `file_synthesis` — Other — https://policylayer.com/tools/agent-store/file-synthesis.md
- `suggest_edges` — Other — https://policylayer.com/tools/agent-store/suggest-edges.md
- `fleet_ping` — Read — https://policylayer.com/tools/agent-store/fleet-ping.md
- `gbrain_brain_stats` — Read — https://policylayer.com/tools/agent-store/gbrain-brain-stats.md
- `gbrain_doctor` — Read — https://policylayer.com/tools/agent-store/gbrain-doctor.md
- `gbrain_get_page` — Read — https://policylayer.com/tools/agent-store/gbrain-get-page.md
- `gbrain_list_pages` — Read — https://policylayer.com/tools/agent-store/gbrain-list-pages.md
- `gbrain_search` — Read — https://policylayer.com/tools/agent-store/gbrain-search.md
- `lint_wiki` — Read — https://policylayer.com/tools/agent-store/lint-wiki.md
- `list_wiki_pages` — Read — https://policylayer.com/tools/agent-store/list-wiki-pages.md
- `read_wiki_page` — Read — https://policylayer.com/tools/agent-store/read-wiki-page.md
- `search_wiki` — Read — https://policylayer.com/tools/agent-store/search-wiki.md
- `synthesize_answer` — Read — https://policylayer.com/tools/agent-store/synthesize-answer.md
- `wiki_stats` — Read — https://policylayer.com/tools/agent-store/wiki-stats.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=agent-store · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/agent-store