lemmy_block_community
Block a community (hide all its posts from your feeds). Rate-limited: 5/hour.
This record as markdown: /tools/kh0pper-crow/lemmy-block-community.md
What lemmy_block_community does on Crow
AI agents use lemmy_block_community to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why lemmy_block_community is rated Medium
Blocking a community modifies the user's account preferences/settings by filtering content from feeds. This is a reversible write operation (communities can typically be unblocked), not destructive. Misuse could suppress legitimate community content from an AI agent's view, but it's account-scoped and rate-limited to 5/hour, limiting blast radius.
From the tool's definition Block a community (hide all its posts from your feeds)
Attacks that exploit this kind of access
The rule that runs lemmy_block_community 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_block_community, this is the rule to start with:
lemmy_block_community stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_block_community call is checked against it from then on.
Questions about lemmy_block_community
Block a community (hide all its posts from your feeds). Rate-limited: 5/hour. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for lemmy_block_community: 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_block_community is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lemmy_block_community 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_block_community. 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_block_community 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