Critical Risk →

delete_all_markers

Delete all markers/memory locations in the session

How to control delete_all_markers ↓

What delete_all_markers does on Pro Tools MCP Server

AI agents call delete_all_markers to permanently remove resources in Pro Tools MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_all_markers needs a policy

This tool performs a bulk deletion operation that cannot be undone. Markers and memory locations in Pro Tools are user-created reference points for navigation and organization within an audio project. Deleting all of them at once is irreversible and would cause loss of important project metadata and workflow organization.

From the tool's definition Tool name 'delete_all_markers' and description 'Delete all markers/memory locations in the session' explicitly indicates irreversible deletion of all markers in a Pro Tools session.

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

How to control delete_all_markers

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

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

delete_all_markers 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 Pro Tools MCP Server — 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 delete_all_markers

What does the delete_all_markers tool do? +

Delete all markers/memory locations in the session. It is categorised as a Destructive tool in the Pro Tools 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 delete_all_markers? +

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

What risk level is delete_all_markers? +

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

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

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

delete_all_markers is provided by the Pro Tools MCP Server MCP server (skrul/protools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pro Tools MCP Server tool call.

Start from Pro Tools MCP Server, 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.

36 Pro Tools MCP Server 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.