Retrieves saved video clips from the Rhombus system. Saved clips can be viewed for up to 2 years and are typically found in the "Clips" tab of the "Saved Video" section of the Rhombus Console. Clips are either manually saved by the user, or automatically by some defined policy. Therefore, this t...
High parameter count (10 properties)
Part of the Rhombus Node MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke clips-tool to trigger processes or run actions in Rhombus Node. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
clips-tool can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
clips-tool:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Rhombus Node policy for all 30 tools.
Agents calling execute-class tools like clips-tool have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
clips-tool is one of the high-risk operations in Rhombus Node. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Retrieves saved video clips from the Rhombus system. Saved clips can be viewed for up to 2 years and are typically found in the "Clips" tab of the "Saved Video" section of the Rhombus Console. Clips are either manually saved by the user, or automatically by some defined policy. Therefore, this tool is not for looking up the events that have occured. This tool allows you to: * Get saved clips or clips expiring soon (filter by devices, locations, search string, time range). * Get all shared live video streams for the organization. * Get all timelapse clips for the organization. Filter options (for saved and expiringSoon only): * Specific devices using their UUIDs (deviceUuidFilters). * Specific locations using their UUIDs (locationUuidFilters). * A simple string search on clip names (searchFilter). * A time range: start (timestampISOAfter) and/or end (timestampISOBefore) timestamp in ISO 8601 format. The tool returns a JSON object with the following structure and important fields: * **errorMsg (string | null):** An error message if the request failed. * **objecterror (boolean | null):** Indicates if an object-level error occurred. * **pageToken (string | null):** A token to be supplied on the next search request to get the next page of results. If this token is null, there is no more data available. * **savedClips (array of objects | null):** An array where each object represents a saved video clip. Each clip object contains the following important fields: * **uuid (string):** The unique identifier for the video clip. * **title (string):** The name given to the video clip. * **description (string | null):** An optional description for the clip. * **timestampMs (int64):** The start time of the video clip in milliseconds since epoch. * **createdAtMs (int64):** The creation timestamp of the clip in milliseconds since epoch. * **createdAtTimestamp (string):** The creation timestamp of the clip in ISO 8601 format. * **deviceUuid (string):** The UUID of the primary device (e.g., camera) that recorded the clip. * **deviceUuids (array of strings or null):** A list of UUIDs for all devices associated with the clip. * **durationSec (int32):** The length of the video clip in seconds. * **status (string):** The current processing status of the clip, with possible values such as INITIATING, UPLOADING, RENDERING, FAILED, COMPLETE, OFFLINE, or UNKNOWN. * **userUuid (string | null):** The UUID of the user associated with the clip, if applicable. * **sourceAlertUuid (string | null):** The UUID of the alert that triggered the creation of this clip, if any. * **sharedLiveVideoStreams (array):** When requestType is sharedLiveStreams, list of shared live video stream objects. * **timelapseClips (array):** When requestType is timelapseClips, list of timelapse clip objects. **Output filtering (all tools):** - `includeFields` (string[]): Dot-notation paths to keep in the response (e.g. `"vehicleEvents.vehicleLicensePlate"`). Omit to return all fields. - `filterBy` (array): Predicates to filter array items. Each entry: `{field, op, value}` where op is one of `= != > >= < <= contains`. All conditions are ANDed. Example: `[{field:"vehicleLicensePlate", op:"=", value:"ABC123"}]` WARNING: some tool responses exceed 400k characters — use these params to request only the data you need.. It is categorised as a Execute tool in the Rhombus Node MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for clips-tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rhombus Node MCP server.
clips-tool 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 clips-tool rule in your Intercept 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 Intercept policy for clips-tool. 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.
clips-tool is provided by the Rhombus Node MCP server (rhombus-node-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept