This tool manages Rhombus door controller rules and door policies. It has the following modes of operation, determined by the "requestType" parameter: - get-door-controller-rules: Get all rules for a specific door controller. Requires doorControllerUuid. - create-door-controller-rule: Create a ...
Single-target operation
Part of the Rhombus Node MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use door-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 door-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.
tools:
door-tool:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Rhombus Node policy for all 30 tools.
Agents calling write-class tools like door-tool have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
This tool manages Rhombus door controller rules and door policies. It has the following modes of operation, determined by the "requestType" parameter: - get-door-controller-rules: Get all rules for a specific door controller. Requires doorControllerUuid. - create-door-controller-rule: Create a new rule for a door controller. Requires doorControllerUuid and ruleConfig (JSON string). - get-door-policies: Get all door alert policies in the organization. - create-door-policy: Create a new door policy. Requires policyName and policyConfig (JSON string). Use the get-entity-tool to find door controller and access controlled door 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 Write tool in the Rhombus Node MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for door-tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rhombus Node MCP server.
door-tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the door-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 door-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.
door-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