schedule_command

Schedule a command to run after a delay (e.g.

SERVEROpenhab SOURCEdeswong/openhab-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deswong-openhab-mcp/schedule-command.md

WHAT IT DOES

What schedule_command does on Openhab

AI agents invoke schedule_command to trigger actions in Openhab. 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.

RISK

Why schedule_command is rated High

The tool schedules and executes commands against the OpenHAB system, which can trigger real-world home automation actions (lights, locks, HVAC, etc.). 'Execute a command' clearly places this in the Execute category. High severity because misuse could trigger unintended physical actions in a home environment, and the scheduling aspect means effects may be delayed and harder to intercept.

From the tool's definition Schedule a command to run after a delay

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs schedule_command safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Openhab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_command, this is the rule to start with:

schedule_command Rate-limited

schedule_command 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": {
    "schedule_command": {
      "limits": [
        {
          "counter": "schedule_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Openhab, apply this rule, and every schedule_command call is checked against it from then on.

FAQ

Questions about schedule_command

What does the schedule_command tool do? +

Schedule a command to run after a delay (e.g. It is categorised as a Execute tool in the Openhab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on schedule_command? +

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

What risk level is schedule_command? +

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

Can I rate-limit schedule_command? +

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

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

schedule_command is provided by the Openhab MCP server (deswong/openhab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Openhab, and thousands of servers like it.

This server

All 25 Openhab tools → High-risk tools on this server →

Across the catalogue

adb_shell_command on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →