This tool performs visual and data searches across Rhombus camera footage and events. It has the following modes of operation, determined by the "requestType" parameter: - license-plate: Search for license plate sightings by plate number. Requires query (the plate number or partial match). - ob...
Accepts freeform code/query input (query); 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 call search-tool to retrieve information from Rhombus Node without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search-tool only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
search-tool:
rules:
- action: allowSee the full Rhombus Node policy for all 30 tools.
Agents calling read-class tools like search-tool have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
This tool performs visual and data searches across Rhombus camera footage and events. It has the following modes of operation, determined by the "requestType" parameter: - license-plate: Search for license plate sightings by plate number. Requires query (the plate number or partial match). - object-by-color: Search for objects by color in camera footage. Requires query (color name) and cameraUuid. - object-by-text: Semantic search for objects in footage using a text description. Requires query (text description). - motion-search: Search for motion events in a camera's field of view. Requires cameraUuid, startTime, and endTime. All search types support optional startTime and endTime to narrow the search window. Use the get-entity-tool with entityType CAMERA to get camera UUIDs. **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 Read tool in the Rhombus Node MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for search-tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rhombus Node MCP server.
search-tool 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 search-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 search-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.
search-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