Removes a track from favorites using its index number from the favorites list.
AI agents call remove_favorite to permanently remove resources in Yit Player — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call remove_favorite doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Yit Player is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Removes a track from favorites using its index number from the favorites list. It is categorised as a Destructive tool in the Yit Player MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Yit Player MCP server in PolicyLayer and add a rule for remove_favorite: 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 Yit Player. Nothing to install.
remove_favorite is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_favorite 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 remove_favorite. 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.
remove_favorite is provided by the Yit Player MCP server (vijayarajparamasivam/yit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.