gts_search

What gts_search does on Crow

AI agents call gts_search to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why gts_search is rated Low

This tool performs read-only queries across the fediverse to retrieve account, hashtag, and status information. There are no side effects, data modification, code execution, or irreversible operations. The rate limit (60/hour) is standard for public search APIs. The primary risk is information disclosure or enumeration, which is low severity given the data queried is typically public on federated social platforms.

From the tool's definition Tool description explicitly states 'Search accounts / hashtags / statuses' and mentions 'Remote queries resolve via WebFinger.' Search operations retrieve data without modification. Rate-limiting indicates the operation is query-based, not mutative.

The rule that runs gts_search safely

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

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

Questions about gts_search