AI agents call list_tracks to retrieve information from Mcp Svstudio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing track information from a project without creating, modifying, deleting, or executing any operations. It is a straightforward read-only action, posing minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'list_tracks' and description states 'List all tracks in the current project' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_tracks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Svstudio, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tracks:
{
"version": "1",
"default": "deny",
"tools": {
"list_tracks": {}
}
}list_tracks 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.
List all tracks in the current project. It is categorised as a Read tool in the Mcp Svstudio MCP Server, which means it retrieves data without modifying state.
Register the Mcp Svstudio MCP server in PolicyLayer and add a rule for list_tracks: 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 Mcp Svstudio. Nothing to install.
list_tracks 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 list_tracks 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 list_tracks. 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.
list_tracks is provided by the Mcp Svstudio MCP server (ocadaruma/mcp-svstudio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Svstudio, 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.
6 Mcp Svstudio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.