Create a new regimen (recurring schedule). regimen_items is a list of {sequence_id, time_offset}. time_offset is milliseconds from midnight of the regimen start day. Example: 21600000 = 6:00am, 43200000 = 12:00pm. To make the regimen actually run, schedule a FarmEvent that targets it via farmbot_...
AI agents use farmbot_add_regimen to create or update resources in Farmbot Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Farmbot Agent environment.
This tool creates a new regimen object that schedules recurring tasks on FarmBot hardware. While it does not immediately execute actions (that requires a paired FarmEvent via farmbot_add_farm_event), it does persistently modify device state by adding a recurring schedule. This is reversible (can be deleted or modified), so it qualifies as Write rather than Execute or Destructive.
From the tool's definition Create a new regimen (recurring schedule)" — the tool creates a recurring automation schedule. Sibling tools include "farmbot_add_farm_event", "farmbot_add_plant", "farmbot_add_sequence", indicating this server manages state changes.
Attacks that exploit this kind of access
Create a new regimen (recurring schedule). regimen_items is a list of {sequence_id, time_offset}. time_offset is milliseconds from midnight of the regimen start day. Example: 21600000 = 6:00am, 43200000 = 12:00pm. To make the regimen actually run, schedule a FarmEvent that targets it via farmbot_add_farm_event with executable_type=. It is categorised as a Write tool in the Farmbot Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Farmbot Agent MCP server in PolicyLayer and add a rule for farmbot_add_regimen: 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.
farmbot_add_regimen 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 farmbot_add_regimen 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.
Set action: deny in the PolicyLayer policy for farmbot_add_regimen. 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.
farmbot_add_regimen 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →