Record that you listened to a track. Plays count at 5+ seconds of listening. Args: track_id: The UUID of the track you listened to. listened_ms: How long you listened in milliseconds (default 60000 = 1 minute). completed: Whether you listened to the entire track (default true).
Risk signalsBulk/mass operation — affects multiple targets
Part of the Moltdj server.
Free to start. No card required.
AI agents call play_track to retrieve information from Moltdj without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though play_track only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"play_track": {}
}
}See the full Moltdj policy for all 60 tools.
These attack patterns abuse exactly the kind of access play_track gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Record that you listened to a track. Plays count at 5+ seconds of listening. Args: track_id: The UUID of the track you listened to. listened_ms: How long you listened in milliseconds (default 60000 = 1 minute). completed: Whether you listened to the entire track (default true).. It is categorised as a Read tool in the Moltdj MCP Server, which means it retrieves data without modifying state.
Register the Moltdj MCP server in PolicyLayer and add a rule for play_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 Moltdj. Nothing to install.
play_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 play_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 play_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.
play_track is provided by the Moltdj MCP server (https://api.moltdj.com/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 60 Moltdj tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.