Create a new empty playlist owned by the authenticated user. privacy_level defaults to
AI agents use fw_create_playlist to create or update resources in Crow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
This tool creates a new playlist resource, which is a reversible write operation. It has minimal blast radius—creating an empty playlist causes no data loss, financial impact, or external command execution. The operation is bounded to the authenticated user's namespace and does not affect system security or other users' data.
From the tool's definition Tool name 'fw_create_playlist' and description 'Create a new empty playlist owned by the authenticated user' indicates a create operation that generates new data.
Documented attack patterns abuse exactly the kind of access fw_create_playlist gives an agent:
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_create_playlist:
{
"version": "1",
"default": "deny",
"tools": {
"fw_create_playlist": {
"limits": [
{
"counter": "fw_create_playlist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fw_create_playlist stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new empty playlist owned by the authenticated user. privacy_level defaults to. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for fw_create_playlist: 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.
fw_create_playlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fw_create_playlist 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.
Set action: deny in the PolicyLayer policy for fw_create_playlist. 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.
fw_create_playlist 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.
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.