AI agents call lexicon_get_track 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 retrieves track metadata and associated data (tags, cuepoints, tempomarkers) from a DJ library without altering state. It is a pure query operation with no side effects, matching the 'Read' category definition. Low severity because misuse would only expose existing library data, not execute code or modify/delete content.
From the tool's definition Tool description states 'Get one track by ID' with 'full payload' retrieval. The server description confirms 'read tools always on' without modification capabilities.
Attacks that exploit this kind of access
Get one track by ID (full payload: tags, cuepoints, tempomarkers, etc.). 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_get_track: 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_get_track 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_get_track 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_get_track. 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_get_track 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 →