AI agents call players to retrieve information from MultiViewer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple retrieval of current player state—listing active players. It has no side effects, makes no modifications, executes no code, and carries no destructive or financial implications. The blast radius of misuse is minimal; an agent querying this information cannot cause harm beyond potentially learning what players are active.
From the tool's definition Tool name 'players' combined with description 'Returns a list of active MultiViewer video players' indicates a query operation that retrieves state information without modifying or executing any operations.
Documented attack patterns abuse exactly the kind of access players 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 players:
{
"version": "1",
"default": "deny",
"tools": {
"players": {}
}
}players is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns a list of active MultiViewer video players. It is categorised as a Read tool in the MultiViewer MCP Server, which means it retrieves data without modifying state.
Register the MultiViewer MCP server in PolicyLayer and add a rule for players: 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.
players is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the players 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 players. 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.
players 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.