Low Risk

fw_get_playlist_tracks

List the tracks in a playlist by id, in playlist order. Each entry has a 0-based

How to control fw_get_playlist_tracks ↓

What fw_get_playlist_tracks does on Crow

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

Low Risk

Why fw_get_playlist_tracks needs a policy

This tool retrieves and queries playlist track data without modifying, deleting, or executing any operations. The action is read-only and returns information about existing playlist content. No blast radius from misuse since it only exposes data that already exists.

From the tool's definition Tool name is 'fw_get_playlist_tracks' and description states 'List the tracks in a playlist by id', which is a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access fw_get_playlist_tracks gives an agent:

How to control fw_get_playlist_tracks

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for fw_get_playlist_tracks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fw_get_playlist_tracks": {}
  }
}

fw_get_playlist_tracks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fw_get_playlist_tracks

What does the fw_get_playlist_tracks tool do? +

List the tracks in a playlist by id, in playlist order. Each entry has a 0-based. 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 fw_get_playlist_tracks? +

Register the Crow MCP server in PolicyLayer and add a rule for fw_get_playlist_tracks: 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 fw_get_playlist_tracks? +

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

Can I rate-limit fw_get_playlist_tracks? +

Yes. Add a rate_limit block to the fw_get_playlist_tracks 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 fw_get_playlist_tracks completely? +

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

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

Enforce policy on every Crow tool call.

Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.