list_tracks

List tracks in a playlist with name, artist, album, and duration.

SERVERIconnect SOURCEiconnect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/list-tracks.md

WHAT IT DOES

What list_tracks does on Iconnect

AI agents call list_tracks to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_tracks is rated Low

This is a straightforward data retrieval operation querying music playlist metadata. It has no side effects, cannot modify or delete data, and presents minimal risk even if an AI agent executes it without explicit user consent. The data returned is limited to non-sensitive music metadata.

From the tool's definition Tool description explicitly states 'List tracks' which retrieves playlist data (name, artist, album, duration) with no modification or deletion indicated.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_tracks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_tracks, this is the rule to start with:

list_tracks Allowed

list_tracks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tracks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every list_tracks call is checked against it from then on.

FAQ

Questions about list_tracks

What does the list_tracks tool do? +

List tracks in a playlist with name, artist, album, and duration. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tracks? +

Register the Iconnect 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 Iconnect. Nothing to install.

What risk level is list_tracks? +

list_tracks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_tracks? +

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.

How do I block list_tracks completely? +

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.

What MCP server provides list_tracks? +

list_tracks is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →