search_tracks
Search tracks in Music library by name, artist, or album.
This record as markdown: /tools/io-github-heznpc-iconnect/search-tracks.md
What search_tracks does on Iconnect
AI agents call search_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.
Why search_tracks is rated Low
The tool performs a search/query against the Music library to retrieve matching tracks. It has no side effects—it does not create, modify, delete, or execute code. The blast radius of misuse is minimal: an agent might retrieve unintended metadata about music in the library, but cannot corrupt data or trigger external actions. This is a straightforward Read category tool.
From the tool's definition Search tracks in Music library by name, artist, or album — this is a query operation that retrieves data without modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
The rule that runs search_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 search_tracks, this is the rule to start with:
search_tracks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every search_tracks call is checked against it from then on.
Questions about search_tracks
Search tracks in Music library by name, artist, or album. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for search_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.
search_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 search_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 search_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.
search_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.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue