lemmy_status

Report Lemmy instance health: site info, federation mode, admin list, user stats, open registrations.

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/lemmy-status.md

WHAT IT DOES

What lemmy_status does on Crow

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

RISK

Why lemmy_status is rated Low

This tool purely retrieves and reports status information about a Lemmy instance. It queries existing data (site info, federation mode, admin list, user statistics, registration status) without creating, modifying, deleting, executing code, or initiating financial transactions.

From the tool's definition Tool description states it 'Report[s] Lemmy instance health: site info, federation mode, admin list, user stats, open registrations' — all read-only queries that retrieve and display information with no modifications or side effects.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lemmy_status 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_status, this is the rule to start with:

lemmy_status Allowed

lemmy_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every lemmy_status call is checked against it from then on.

FAQ

Questions about lemmy_status

What does the lemmy_status tool do? +

Report Lemmy instance health: site info, federation mode, admin list, user stats, open registrations. 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_status? +

Register the Crow MCP server in PolicyLayer and add a rule for lemmy_status: 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_status? +

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

Can I rate-limit lemmy_status? +

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

Set action: deny in the PolicyLayer policy for lemmy_status. 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_status? +

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

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →