# list_comments

List comments for a live FastDrop product by its slug, as a two-level tree (top-level comments and their replies). Removed comments appear as a {deleted: true} tombstone. Unauthenticated - available to any agent.

Agent View of the PolicyLayer registry record for `list_comments`. HTML page: https://policylayer.com/tools/dev-fastdrop-fastdrop/list-comments

## Facts

- Tool: `list_comments`
- Server: Fastdrop (`https://fastdrop.dev/mcp`) — https://policylayer.com/tools/dev-fastdrop-fastdrop.md
- Homepage: https://github.com/https://fastdrop.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `slug` | string | yes | Product slug |
| `limit` | number | no | Max top-level results, 1-50, default 20 |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_comments",
    "arguments": {
      "slug": "<slug>"
    }
  }
}
```

## Why list_comments is rated Low

Even though list_comments only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call list_comments to retrieve information from Fastdrop without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Fastdrop:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_comments": {}
  }
}
```

## Other tools on Fastdrop (5)

- `find_tools` — Read — https://policylayer.com/tools/dev-fastdrop-fastdrop/find-tools.md
- `get_product` — Read — https://policylayer.com/tools/dev-fastdrop-fastdrop/get-product.md
- `list_launches` — Read — https://policylayer.com/tools/dev-fastdrop-fastdrop/list-launches.md
- `list_reviews` — Read — https://policylayer.com/tools/dev-fastdrop-fastdrop/list-reviews.md
- `search_products` — Read — https://policylayer.com/tools/dev-fastdrop-fastdrop/search-products.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-fastdrop-fastdrop · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-fastdrop-fastdrop