smart_entry_sequence · Nuki MCP: Risk & Policy

WHAT IT DOES

What smart_entry_sequence does on Nuki

AI agents invoke smart_entry_sequence to trigger actions in Nuki. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why smart_entry_sequence needs a policy

This tool executes a complex, multi-step sequence of actions on physical security devices (door buzzer and smart lock). While not destructive (actions are reversible—locks can be re-locked, buzzers reset), it goes beyond simple Read or Write operations by orchestrating sequential external commands that alter physical access state.

From the tool's definition Tool description states 'Execute a full entry sequence: Buzz the main building door and then unlock the apartment door.' The verb 'Execute' combined with triggering multiple physical actions (buzzing and unlocking) on real-world devices indicates this…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

smart_entry_sequence Rate-limited

smart_entry_sequence stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "smart_entry_sequence": {
      "limits": [
        {
          "counter": "smart_entry_sequence_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nuki, so you can run agents against it safely.

FAQ

Questions about smart_entry_sequence

What does the smart_entry_sequence tool do? +

Execute a full entry sequence: Buzz the main building door and then unlock the apartment door. It is categorised as a Execute tool in the Nuki MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on smart_entry_sequence? +

Register the Nuki MCP server in PolicyLayer and add a rule for smart_entry_sequence: 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 Nuki. Nothing to install.

What risk level is smart_entry_sequence? +

smart_entry_sequence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit smart_entry_sequence? +

Yes. Add a rate_limit block to the smart_entry_sequence 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 smart_entry_sequence completely? +

Set action: deny in the PolicyLayer policy for smart_entry_sequence. 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 smart_entry_sequence? +

smart_entry_sequence is provided by the Nuki MCP server (sandraschi/nuki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.