# repository_search

Search for documents in the DeSo repository

Agent View of the PolicyLayer registry record for `repository_search`. HTML page: https://policylayer.com/tools/deso-protocol-deso-mcp/repository-search

## Facts

- Tool: `repository_search`
- Server: DeSo MCP Server (`deso-protocol/deso-mcp`) — https://policylayer.com/tools/deso-protocol-deso-mcp.md
- Homepage: https://github.com/deso-protocol/deso-mcp
- Risk category: Read (Low risk)
- Registry record: grade B, 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": "repository_search",
    "arguments": {}
  }
}
```

## Why repository_search is rated Low

The tool performs a read-only search operation across repository documents. It has no side effects, does not modify data, execute code, or perform destructive actions. The blast radius of misuse is minimal — an agent could retrieve documentation but cannot cause harm through retrieval alone. This is a standard Read category tool.

From the tool's own definition: "Tool name is 'repository_search' and description states it 'Search for documents in the DeSo repository' — this is a query operation that retrieves information without modifying, deleting, or executing code."

## Use case

AI agents call repository_search to retrieve information from DeSo 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 DeSo MCP Server:

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

## Other tools on DeSo MCP Server (9)

- `deso_api_explorer` — Read — https://policylayer.com/tools/deso-protocol-deso-mcp/deso-api-explorer.md
- `deso_debugging_guide` — Read — https://policylayer.com/tools/deso-protocol-deso-mcp/deso-debugging-guide.md
- `deso_graphql_helper` — Read — https://policylayer.com/tools/deso-protocol-deso-mcp/deso-graphql-helper.md
- `deso_implementation_patterns` — Read — https://policylayer.com/tools/deso-protocol-deso-mcp/deso-implementation-patterns.md
- `deso_js_guide` — Read — https://policylayer.com/tools/deso-protocol-deso-mcp/deso-js-guide.md
- `deso_ui_components` — Read — https://policylayer.com/tools/deso-protocol-deso-mcp/deso-ui-components.md
- `explain_deso_architecture` — Read — https://policylayer.com/tools/deso-protocol-deso-mcp/explain-deso-architecture.md
- `read_repository_document` — Read — https://policylayer.com/tools/deso-protocol-deso-mcp/read-repository-document.md
- `generate_deso_code` — Write — https://policylayer.com/tools/deso-protocol-deso-mcp/generate-deso-code.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=deso-protocol-deso-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deso-protocol-deso-mcp