lexicon_update_track · Lexicon MCP: Risk & Policy

WHAT IT DOES

What lexicon_update_track does on Lexicon

AI agents use lexicon_update_track to create or update resources in Lexicon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lexicon environment.

WHY IT NEEDS A POLICY

Why lexicon_update_track needs a policy

This tool modifies track data (tags, metadata, cuepoints, incoming flag) within a DJ library. These are reversible changes—metadata and tags can be updated again or reverted. There is no deletion or destruction of data, no code execution, and no financial impact.

From the tool's definition Tool description states 'Update one track (tags, metadata, cuepoints, incoming flag)'. The verbs 'update' and 'metadata' modification are characteristic of Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lexicon_update_track Rate-limited

lexicon_update_track stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lexicon_update_track": {
      "limits": [
        {
          "counter": "lexicon_update_track_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lexicon, so you can run agents against it safely.

FAQ

Questions about lexicon_update_track

What does the lexicon_update_track tool do? +

Update one track (tags, metadata, cuepoints, incoming flag). Requires LEXICON_MCP_ALLOW_WRITES=1. It is categorised as a Write tool in the Lexicon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lexicon_update_track? +

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

What risk level is lexicon_update_track? +

lexicon_update_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lexicon_update_track? +

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

How do I block lexicon_update_track completely? +

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

What MCP server provides lexicon_update_track? +

lexicon_update_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.