vss-query-analytics

To query video analytics incidents and metrics from a VA-MCP endpoint, you must use a two-step pattern: initialize a session to obtain a session ID, then call the endpoint with that session header for read-only retrieval.

No, you cannot trigger deployments or VLM interactions using this VA-MCP access method. It enforces read-only retrieval for incidents, metrics, and sensor data while actively blocking deployment or VLM-triggered workflows.

Retrieving video analytics sensor data requires a two-step session pattern: first initialize the connection to get a session ID, then execute a tools/call request with the session header to securely fetch the sensor data.

Yes, VA-MCP query access supports read-only monitoring and QA workflows by enabling secure, repeatable queries for video analytics alerts and incidents without executing deployment or VLM actions.

Using the two-step VA-MCP pattern, you can retrieve video analytics incidents, metrics, sensor data, and alerts. This read-only access is suitable for building dashboards, conducting audits, and performing QA checks.

The main limitation of accessing video analytics data through VA-MCP guardrails is the strict enforcement of read-only actions, which blocks any attempts to trigger deployments or VLM interactions to prevent untrusted actions.