Low Risk

lemmy_search

Search across communities, posts, comments, users. Rate-limited: 60/hour.

How to control lemmy_search ↓

What lemmy_search does on Crow

AI agents call lemmy_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.

Low Risk

Why lemmy_search needs a policy

This tool retrieves or queries data without side effects. It performs searches across Lemmy (a federated social platform) content, returning results without modifying, creating, deleting, or executing any operations. The rate limiting indicates it is a passive read operation designed to prevent abuse of query volume rather than to protect against destructive actions.

From the tool's definition Tool name is 'lemmy_search' and description explicitly states it 'Search[es] across communities, posts, comments, users' with rate limiting noted.

Documented attack patterns abuse exactly the kind of access lemmy_search gives an agent:

How to control lemmy_search

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 lemmy_search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lemmy_search": {}
  }
}

lemmy_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about lemmy_search

What does the lemmy_search tool do? +

Search across communities, posts, comments, users. Rate-limited: 60/hour. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lemmy_search? +

Register the Crow MCP server in PolicyLayer and add a rule for lemmy_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.

What risk level is lemmy_search? +

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

Can I rate-limit lemmy_search? +

Yes. Add a rate_limit block to the lemmy_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 lemmy_search completely? +

Set action: deny in the PolicyLayer policy for lemmy_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 lemmy_search? +

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

Enforce policy on every Crow tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.