farmbot_reboot · Farmbot Agent MCP: Risk & Policy

WHAT IT DOES

What farmbot_reboot does on Farmbot Agent

AI agents invoke farmbot_reboot to trigger actions in Farmbot Agent. 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 farmbot_reboot needs a policy

Rebooting triggers an external hardware operation that causes the device to go offline, disrupts active connections, and interrupts any in-progress gardening tasks. This is an Execute action with high severity because misuse could disrupt critical farming operations (e.g., watering cycles, plant care routines) and requires reconnection afterward.

From the tool's definition Reboot the FarmBot device. Restarts the FarmBot OS. The device will be offline for 1-2 minutes during reboot. The MQTT connection will be lost and must be re-established after reboot.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

farmbot_reboot Rate-limited

farmbot_reboot 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": {
    "farmbot_reboot": {
      "limits": [
        {
          "counter": "farmbot_reboot_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 Farmbot Agent, so you can run agents against it safely.

FAQ

Questions about farmbot_reboot

What does the farmbot_reboot tool do? +

Reboot the FarmBot device. Restarts the FarmBot OS. The device will be offline for 1-2 minutes during reboot. Use this to recover from stuck states or apply firmware updates. The MQTT connection will be lost and must be re-established after reboot. It is categorised as a Execute tool in the Farmbot Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on farmbot_reboot? +

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

What risk level is farmbot_reboot? +

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

Can I rate-limit farmbot_reboot? +

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

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

farmbot_reboot is provided by the Farmbot Agent MCP server (kieranklaassen/farmbot-agent-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.