# export_playlist

Export a playlist as JSON or CSV

Agent View of the PolicyLayer registry record for `export_playlist`. HTML page: https://policylayer.com/tools/4shil-ytm-mcp/export-playlist

## Facts

- Tool: `export_playlist`
- Server: Ytm (`4shil/ytm-mcp`) — https://policylayer.com/tools/4shil-ytm-mcp.md
- Homepage: https://github.com/4shil/ytm-mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "export_playlist",
    "arguments": {}
  }
}
```

## Why export_playlist is rated Low

Exporting a playlist is a read operation that retrieves playlist data and converts it to a portable format (JSON or CSV). It does not modify, delete, or create any data on the service, nor does it trigger any external operations or financial transactions.

From the tool's own definition: "'Export a playlist as JSON or CSV' — reads and serializes playlist data into a file format, no modification or deletion implied"

## Use case

AI agents call export_playlist to retrieve information from Ytm 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 Ytm:

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

## Other tools on Ytm (11)

- `play_song` — Execute — https://policylayer.com/tools/4shil-ytm-mcp/play-song.md
- `playback_control` — Execute — https://policylayer.com/tools/4shil-ytm-mcp/playback-control.md
- `download_history` — Read — https://policylayer.com/tools/4shil-ytm-mcp/download-history.md
- `get_current_song` — Read — https://policylayer.com/tools/4shil-ytm-mcp/get-current-song.md
- `get_history` — Read — https://policylayer.com/tools/4shil-ytm-mcp/get-history.md
- `list_downloads` — Read — https://policylayer.com/tools/4shil-ytm-mcp/list-downloads.md
- `list_playlists` — Read — https://policylayer.com/tools/4shil-ytm-mcp/list-playlists.md
- `search_song` — Read — https://policylayer.com/tools/4shil-ytm-mcp/search-song.md
- `add_to_playlist` — Write — https://policylayer.com/tools/4shil-ytm-mcp/add-to-playlist.md
- `create_playlist` — Write — https://policylayer.com/tools/4shil-ytm-mcp/create-playlist.md
- `download_song` — Write — https://policylayer.com/tools/4shil-ytm-mcp/download-song.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=4shil-ytm-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/4shil-ytm-mcp