This tool manages Rhombus automation rules for triggering actions based on events. It has the following modes of operation, determined by the "requestType" parameter: - list: List all automation rules in the organization. - create: Create a new automation rule. Requires ruleName and ruleConfig ...
Single-target operation
Part of the Rhombus Node MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call rules-tool to permanently remove or destroy resources in Rhombus Node. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call rules-tool in a loop, permanently destroying resources in Rhombus Node. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
rules-tool:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Rhombus Node policy for all 30 tools.
Agents calling destructive-class tools like rules-tool have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
rules-tool is one of the critical-risk operations in Rhombus Node. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
This tool manages Rhombus automation rules for triggering actions based on events. It has the following modes of operation, determined by the "requestType" parameter: - list: List all automation rules in the organization. - create: Create a new automation rule. Requires ruleName and ruleConfig (JSON string with the rule definition). - update: Update an existing rule. Requires ruleUuid and ruleConfig (JSON string with updated fields). - delete: Delete a rule. Requires ruleUuid. - get-records: Get the event trigger history for a specific rule. Requires ruleUuid. Rules can trigger notifications, recordings, and other actions based on events from cameras, sensors, doors, etc. **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 Destructive tool in the Rhombus Node MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for rules-tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rhombus Node MCP server.
rules-tool is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rules-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 rules-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.
rules-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