AI agents call lexicon_list_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.
This tool queries and retrieves track data from a DJ library with pagination support. It performs no modifications, deletions, or execution of code—purely a read operation. The low severity reflects minimal blast radius if misused; an AI agent listing tracks cannot damage the library or cause unintended side effects.
From the tool's definition Tool name 'lexicon_list_tracks' and description 'List tracks from the Lexicon library (paginated, newest first)' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List tracks from the Lexicon library (paginated, newest first). It is categorised as a Read tool in the Lexicon MCP Server, which means it retrieves data without modifying state.
Register the Lexicon MCP server in PolicyLayer and add a rule for lexicon_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 Lexicon. Nothing to install.
lexicon_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 lexicon_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 lexicon_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.
lexicon_list_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.
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 →