lemmy_feed
Fetch posts. type_: Subscribed (follows), Local (this instance), All (federated). Rate-limited: 60/hour.
This record as markdown: /tools/kh0pper-crow/lemmy-feed.md
What lemmy_feed does on Crow
AI agents call lemmy_feed 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 lemmy_feed is rated Low
This tool retrieves data from a Lemmy feed without modifying, deleting, or executing operations. It is a straightforward read operation with no side effects. The rate limit suggests it is designed as a data retrieval endpoint. Severity is low because fetching posts poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Fetch posts' with options for Subscribed, Local, or All feeds. Rate-limiting (60/hour) is consistent with a read-only query operation.
Attacks that exploit this kind of access
The rule that runs lemmy_feed 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 lemmy_feed, this is the rule to start with:
lemmy_feed is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every lemmy_feed call is checked against it from then on.
Questions about lemmy_feed
Fetch posts. type_: Subscribed (follows), Local (this instance), All (federated). 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 lemmy_feed: 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.
lemmy_feed 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 lemmy_feed 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 lemmy_feed. 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.
lemmy_feed 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue