# list_categories

List all categories in your Zype library. Call this FIRST when filtering videos by category. Categories organize videos by attributes like Genre, Premium status, YouTube Channel, etc. Each category has a title and list of possible values. Workflow for category-based video queries: 1. Call list_categories to see available category titles and their values 2. Use list_videos with category filter: {"category": {"CategoryTitle": "value"}} Example: To find "Saturday Night Live" videos: 1. list_categories → shows "YouTube Channel" category with "Saturday Night Live" as a value 2. list_videos with {"category": {"YouTube Channel": "Saturday Night Live"}}

Agent View of the PolicyLayer registry record for `list_categories`. HTML page: https://policylayer.com/tools/com-zype-mcp-server/list-categories

## Facts

- Tool: `list_categories`
- Server: Zype Com (`zype/zype-mcp`) — https://policylayer.com/tools/com-zype-mcp-server.md
- Homepage: https://github.com/zype/zype-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity verified
- Server auth posture: gated_ambiguous
- Server rate-limited: no
- Parameters: 6
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `page` | number | no | Page number (default: 1) |
| `sort` | string | no | Field to sort by |
| `order` | string | no | Sort order |
| `title` | string | no | Filter by title |
| `per_page` | number | no | Results per page (default: 10, max: 500) |
| `friendly_title` | string | no | Filter by friendly title (slug) |

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_categories",
    "arguments": {}
  }
}
```

## Why list_categories is rated Low

Even though list_categories 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_categories to retrieve information from Zype Com 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 Zype Com:

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

## Other tools on Zype Com (295)

- `cancel_subscription` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/cancel-subscription.md
- `delete_ad_tag` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-ad-tag.md
- `delete_ad_timing` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-ad-timing.md
- `delete_category` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-category.md
- `delete_consumer` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-consumer.md
- `delete_content_rule_group` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-content-rule-group.md
- `delete_content_rule_profile` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-content-rule-profile.md
- `delete_live_encoder` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-live-encoder.md
- `delete_live_event` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-live-event.md
- `delete_plan` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-plan.md
- `delete_playlist` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-playlist.md
- `delete_playlist_entitlement` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-playlist-entitlement.md
- `delete_program_guide` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-program-guide.md
- `delete_redemption_code` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-redemption-code.md
- `delete_segment` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-segment.md
- `delete_self_hosted_source` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-self-hosted-source.md
- `delete_subscription` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subscription.md
- `delete_subtitle` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subtitle.md
- `delete_subtitle_playlist` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subtitle-playlist.md
- `delete_transaction` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-transaction.md
- `delete_video` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video.md
- `delete_video_entitlement` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-entitlement.md
- `delete_video_favorite` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-favorite.md
- `delete_video_source` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-source.md
- `delete_zobject` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-zobject.md
- `delete_zobject_type` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-zobject-type.md
- `playout_delete_ad_timing` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-ad-timing.md
- `playout_delete_all_ad_timings` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-all-ad-timings.md
- `playout_delete_block` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-block.md
- `playout_delete_channel` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-channel.md
- …and 265 more: https://policylayer.com/tools/com-zype-mcp-server.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=com-zype-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-zype-mcp-server