lemmy_review_reports
List open post + comment reports (admin / mod only). Read-only summary.
This record as markdown: /tools/kh0pper-crow/lemmy-review-reports.md
What lemmy_review_reports does on Crow
AI agents call lemmy_review_reports 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_review_reports is rated Low
This tool retrieves and displays existing report data without modifying, deleting, or executing any actions. It is restricted to admin/mod roles, limiting access. The read-only nature and retrieval-only purpose classify it as a Read operation with low severity due to access controls and absence of data modification capabilities.
From the tool's definition Tool description explicitly states 'List open post + comment reports (admin / mod only). Read-only summary.' The terms 'List' and 'Read-only' clearly indicate data retrieval with no side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs lemmy_review_reports 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_review_reports, this is the rule to start with:
lemmy_review_reports 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_review_reports call is checked against it from then on.
Questions about lemmy_review_reports
List open post + comment reports (admin / mod only). Read-only summary. 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_review_reports: 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_review_reports 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_review_reports 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_review_reports. 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_review_reports 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