AI agents call player_delete to permanently remove resources in MultiViewer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation. Once a video player is deleted, the action cannot be easily undone without recreating it. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.
From the tool's definition Tool name 'player_delete' and description 'Deletes a MultiViewer video player' explicitly indicate irreversible deletion of a player instance.
Documented attack patterns abuse exactly the kind of access player_delete 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_delete:
{
"version": "1",
"default": "deny",
"hide": [
"player_delete"
]
}player_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes a MultiViewer video player. It is categorised as a Destructive tool in the MultiViewer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MultiViewer MCP server in PolicyLayer and add a rule for player_delete: 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_delete 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 player_delete 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_delete. 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_delete 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.