AI agents call show_live_video to retrieve information from MCP Server - VMS Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server context (CCTV/VMS system) and sibling tools like 'fetch_live_image', 'get_channels', this tool most likely retrieves or displays a live video stream — a read operation. However, 'show' could imply triggering a UI/playback dialog (the server description mentions 'manage playback dialogs'), which edges toward Execute. With an empty description, confidence is reduced.
From the tool's definition Tool name 'show_live_video' on a VMS server that 'retrieve live and recorded video streams'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access show_live_video gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server - VMS Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for show_live_video:
{
"version": "1",
"default": "deny",
"tools": {
"show_live_video": {}
}
}show_live_video 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.
show_live_video. It is categorised as a Read tool in the MCP Server - VMS Integration MCP Server, which means it retrieves data without modifying state.
Register the MCP Server - VMS Integration MCP server in PolicyLayer and add a rule for show_live_video: 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 MCP Server - VMS Integration. Nothing to install.
show_live_video 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 show_live_video 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 show_live_video. 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.
show_live_video is provided by the MCP Server - VMS Integration MCP server (jyjune/mcp_vms). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server - VMS Integration, 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.
16 MCP Server - VMS Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.