AI agents call get_markers to retrieve information from Pro Tools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves data (markers/memory locations) from the session without creating, modifying, deleting, or executing any operations. It is a pure read operation with no destructive or side-effect-inducing capability. The low severity reflects minimal risk—exposing marker metadata poses no blast radius to session integrity or external systems.
From the tool's definition Tool name 'get_markers' and description 'Get all memory locations/markers in the session' indicate a retrieval operation with no side effects. It queries existing markers from a Pro Tools session.
Documented attack patterns abuse exactly the kind of access get_markers gives an agent:
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 get_markers:
{
"version": "1",
"default": "deny",
"tools": {
"get_markers": {}
}
}get_markers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all memory locations/markers in the session. It is categorised as a Read tool in the Pro Tools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pro Tools MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_markers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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.