Medium Risk

update-tool

This tool allows updating configuration settings for various Rhombus entities. Currently supports: - **Cameras**: Update video settings (resolution, HDR, WDR, brightness, contrast, etc.), audio settings (recording, microphone, speaker), and device settings (name, timezone, LED control). For LED...

Part of the Rhombus Node MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

rhombus-node-mcp Write Risk 2/5

AI agents use update-tool to create or modify resources in Rhombus Node. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call update-tool repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Rhombus Node.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

rhombus-node.yaml
tools:
  update-tool:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Rhombus Node policy for all 30 tools.

Tool Name update-tool
Category Write
Risk Level Medium

View all 30 tools →

Agents calling write-class tools like update-tool have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the update-tool tool do? +

This tool allows updating configuration settings for various Rhombus entities. Currently supports: - **Cameras**: Update video settings (resolution, HDR, WDR, brightness, contrast, etc.), audio settings (recording, microphone, speaker), and device settings (name, timezone, LED control). For LED control, use EXACTLY these field names in cameraDeviceSettings: - To turn LED off: {"led_stealth_mode": true} (recommended) or {"led_mode": "always_off"} - To turn LED on: {"led_stealth_mode": false} or {"led_mode": "always_on"} or {"led_mode": "auto"} - IMPORTANT: Use underscore in field names (led_mode, led_stealth_mode), not camelCase The tool supports faceted UUIDs (e.g., "cameraUuid.v0" or "cameraUuid.v1") to update specific camera facets. If no facet is specified, defaults to "v0". The tool guides users through a multi-step process: 1. Entity selection (if not provided) 2. Settings configuration with current values shown 3. Confirmation and application of changes Future support planned for: - Climate sensors - Door controllers - Environmental gateways - Audio gateways - Doorbell cameras - Badge readers The tool uses elicitation forms for rich user interaction and shows current settings before updates. **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 Write tool in the Rhombus Node MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update-tool? +

Add a rule in your Intercept YAML policy under the tools section for update-tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rhombus Node MCP server.

What risk level is update-tool? +

update-tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update-tool? +

Yes. Add a rate_limit block to the update-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.

How do I block update-tool completely? +

Set action: deny in the Intercept policy for update-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.

What MCP server provides update-tool? +

update-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.

Enforce policies on Rhombus Node

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.