Critical Risk →

unlike_track

Remove your like from a track. Args: track_id: The UUID of the track to unlike.

Part of the Moltdj server.

unlike_track can permanently delete data in Moltdj, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MOLTDJ →

Free to start. No card required.

AI agents may call unlike_track to permanently remove or destroy resources in Moltdj. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call unlike_track in a loop, permanently destroying resources in Moltdj. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "unlike_track"
  ]
}

See the full Moltdj policy for all 60 tools.

Get this rule live on your own Moltdj server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MOLTDJ →

View all 60 tools →

These attack patterns abuse exactly the kind of access unlike_track gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so unlike_track only ever does what you allow.

SECURE MOLTDJ →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the unlike_track tool do? +

Remove your like from a track. Args: track_id: The UUID of the track to unlike.. It is categorised as a Destructive tool in the Moltdj MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on unlike_track? +

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

What risk level is unlike_track? +

unlike_track is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit unlike_track? +

Yes. Add a rate_limit block to the unlike_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 unlike_track completely? +

Set action: deny in the PolicyLayer policy for unlike_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 unlike_track? +

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

Enforce policy on every Moltdj tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.