New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

fl_delete_marker

Delete a marker from the playlist.

SERVERFL Studio MCP Server SOURCE404kidwiz/fl-studio-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/404kidwiz-fl-studio-mcp/fl-delete-marker.md

What fl_delete_marker does on FL Studio MCP Server

AI agents call fl_delete_marker to permanently remove resources in FL Studio MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why fl_delete_marker is rated Critical

The tool permanently removes a marker object from FL Studio's playlist. Markers are project organization artifacts that users create and rely on; deletion cannot be undone without undo history. While the blast radius is narrower than deleting entire tracks or projects, it still constitutes irreversible data loss. Destructive is the appropriate category per the rules (Destructive > Execute > Write > Read).

From the tool's definition Tool name contains 'delete' and description states 'Delete a marker from the playlist' — this is an irreversible removal of data.

Questions about fl_delete_marker

What does the fl_delete_marker tool do? +

Delete a marker from the playlist. It is categorised as a Destructive tool in the FL Studio MCP Server 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 fl_delete_marker? +

Register the FL Studio MCP Server MCP server in PolicyLayer and add a rule for fl_delete_marker: 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 FL Studio MCP Server. Nothing to install.

What risk level is fl_delete_marker? +

fl_delete_marker 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 fl_delete_marker? +

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

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

fl_delete_marker is provided by the FL Studio MCP Server MCP server (404kidwiz/fl-studio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on FL Studio MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FL Studio MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.