AI agents invoke player_seek_to to trigger actions in MultiViewer. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the name, this tool likely seeks/scrubs a media player to a specific position or timestamp. This triggers an external operation on the MultiViewer application (changing playback position), placing it in the Execute category. Severity is medium as misuse could disrupt viewing experience but has limited broader impact. Confidence is low due to empty description.
From the tool's definition Tool name 'player_seek_to' on a media player MCP server; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access player_seek_to gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MultiViewer, and nothing reaches the server without passing your rules. This is the rule we recommend for player_seek_to:
{
"version": "1",
"default": "deny",
"tools": {
"player_seek_to": {
"limits": [
{
"counter": "player_seek_to_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}player_seek_to stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
player_seek_to. It is categorised as a Execute tool in the MultiViewer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MultiViewer MCP server in PolicyLayer and add a rule for player_seek_to: 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 MultiViewer. Nothing to install.
player_seek_to is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the player_seek_to 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 player_seek_to. 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.
player_seek_to is provided by the MultiViewer MCP server (robspectre/mvf1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MultiViewer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 MultiViewer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.