lexicon_search_tracks

Search tracks using Lexicon filters. Examples: - {

Server Lexicon turbotailz/lexicon-mcp
Category Read
Risk class Low
Parameters 00 required

What lexicon_search_tracks does on Lexicon

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

Why lexicon_search_tracks needs a policy

This tool searches and retrieves track data from the Lexicon DJ library. It performs a read-only operation with no side effects—it queries existing data without creating, modifying, deleting, or executing external operations. The 'search' verb and filter-based retrieval confirm it is a Read category tool.

From the tool's definition Tool name 'lexicon_search_tracks' and description 'Search tracks using Lexicon filters' indicate a query operation that retrieves data without modification.

Questions about lexicon_search_tracks

What does the lexicon_search_tracks tool do? +

Search tracks using Lexicon filters. Examples: - {. It is categorised as a Read tool in the Lexicon MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lexicon_search_tracks? +

Register the Lexicon MCP server in PolicyLayer and add a rule for lexicon_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 Lexicon. Nothing to install.

What risk level is lexicon_search_tracks? +

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

Can I rate-limit lexicon_search_tracks? +

Yes. Add a rate_limit block to the lexicon_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.

How do I block lexicon_search_tracks completely? +

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

What MCP server provides lexicon_search_tracks? +

lexicon_search_tracks is provided by the Lexicon MCP server (turbotailz/lexicon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.