gts_review_reports

List pending moderation reports (local + federated). Read-only.

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/gts-review-reports.md

WHAT IT DOES

What gts_review_reports does on Crow

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

RISK

Why gts_review_reports is rated Low

This tool retrieves and queries moderation reports without creating, modifying, deleting, or executing any operations. The explicit 'Read-only' designation confirms it has no side effects. While moderation reports may contain sensitive information, the tool itself poses minimal risk as it merely displays existing data.

From the tool's definition Tool name 'gts_review_reports' combined with description 'List pending moderation reports (local + federated). Read-only.' indicates data retrieval with explicit read-only constraint.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gts_review_reports Allowed

gts_review_reports 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": {
    "gts_review_reports": {}
  }
}

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 gts_review_reports call is checked against it from then on.

FAQ

Questions about gts_review_reports

What does the gts_review_reports tool do? +

List pending moderation reports (local + federated). Read-only. 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 gts_review_reports? +

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

What risk level is gts_review_reports? +

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

Can I rate-limit gts_review_reports? +

Yes. Add a rate_limit block to the gts_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.

How do I block gts_review_reports completely? +

Set action: deny in the PolicyLayer policy for gts_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.

What MCP server provides gts_review_reports? +

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

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

review_changes on MCP Server PR Pilot → The MCP Attack Database →

Guides

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