Search accounts / hashtags / statuses across the fediverse. Remote queries resolve via WebFinger. Rate-limited: 60/hour.
AI agents call gts_search to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from the fediverse without any side effects or data modification capabilities. It is a straightforward search/query function with rate-limiting (60/hour), making it a Read category tool. The severity is low because search operations have minimal risk of harm even if misused—the worst case would be information discovery or enumeration of public data on federated networks.
From the tool's definition Tool performs search operations across the fediverse for accounts, hashtags, and statuses. The description explicitly states it 'Search' accounts/hashtags/statuses and uses WebFinger for remote queries, which are read-only operations.
Documented attack patterns abuse exactly the kind of access gts_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for gts_search:
{
"version": "1",
"default": "deny",
"tools": {
"gts_search": {}
}
} gts_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search accounts / hashtags / statuses across the fediverse. Remote queries resolve via WebFinger. Rate-limited: 60/hour. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for gts_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 Crow. Nothing to install.
gts_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gts_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.
Set action: deny in the PolicyLayer policy for gts_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.
gts_search is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.