Medium Risk

door-tool

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

Part of the Rhombus Node server.

door-tool can modify Rhombus Node data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE RHOMBUS NODE →

Free to start. No card required.

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. PolicyLayer'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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "door-tool": {
      "limits": [
        {
          "counter": "door-tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Rhombus Node policy for all 31 tools.

Get this rule live on your own Rhombus Node server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY RHOMBUS NODE →

View all 31 tools →

These attack patterns abuse exactly the kind of access door-tool gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so door-tool only ever does what you allow.

SECURE RHOMBUS NODE →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the door-tool tool do? +

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.

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

Register the Rhombus Node MCP server in PolicyLayer and add a rule for door-tool: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rhombus Node. Nothing to install.

What risk level is door-tool? +

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

Can I rate-limit door-tool? +

Yes. Add a rate_limit block to the door-tool rule in your PolicyLayer 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 door-tool completely? +

Set action: deny in the PolicyLayer 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.

What MCP server provides door-tool? +

door-tool is provided by the Rhombus Node MCP server (rhombus-node-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Rhombus Node tool call.

Deterministic rules across all 31 Rhombus Node tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.