Critical Risk →

crow_remove_from_setlist

Remove a song from a setlist

How to control crow_remove_from_setlist ↓

What crow_remove_from_setlist does on Crow

AI agents call crow_remove_from_setlist to permanently remove resources in Crow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why crow_remove_from_setlist needs a policy

The tool removes an item from a setlist, which is a deletion/removal operation. While not catastrophic (it's removing a song entry from a list rather than deleting files or system data), the removal is likely irreversible without a separate restore operation. The word 'remove' indicates a destructive action on managed data.

From the tool's definition Remove a song from a setlist

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

How to control crow_remove_from_setlist

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 crow_remove_from_setlist:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "crow_remove_from_setlist"
  ]
}

crow_remove_from_setlist disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crow_remove_from_setlist

What does the crow_remove_from_setlist tool do? +

Remove a song from a setlist. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on crow_remove_from_setlist? +

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

crow_remove_from_setlist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit crow_remove_from_setlist? +

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

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

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