repository_search

Search for documents in the DeSo repository

SERVERDeSo MCP Server SOURCEdeso-protocol/deso-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/deso-protocol-deso-mcp/repository-search.md

WHAT IT DOES

What repository_search does on DeSo MCP Server

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.

RISK

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 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs repository_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and DeSo MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For repository_search, this is the rule to start with:

repository_search Allowed

repository_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DeSo MCP Server, apply this rule, and every repository_search call is checked against it from then on.

FAQ

Questions about repository_search

What does the repository_search tool do? +

Search for documents in the DeSo repository. It is categorised as a Read tool in the DeSo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on repository_search? +

Register the DeSo MCP Server MCP server in PolicyLayer and add a rule for repository_search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches DeSo MCP Server. Nothing to install.

What risk level is repository_search? +

repository_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit repository_search? +

Yes. Add a rate_limit block to the repository_search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block repository_search completely? +

Set action: deny in the PolicyLayer policy for repository_search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides repository_search? +

repository_search is provided by the DeSo MCP Server MCP server (deso-protocol/deso-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on DeSo MCP Server, and thousands of servers like it.

This server

All 10 DeSo MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →