Resumes playing the currently paused track.
AI agents use resume_music to create or update resources in Yit Player — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yit Player environment.
An AI agent can call resume_music faster than any human can review — one bad instruction and it creates or modifies resources in Yit Player by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Resumes playing the currently paused track. It is categorised as a Write tool in the Yit Player MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yit Player MCP server in PolicyLayer and add a rule for resume_music: 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.
resume_music is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resume_music 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 resume_music. 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.
resume_music 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.