Execute a saved sequence on the FarmBot device via MQTT. Runs the sequence identified by ID. The sequence must already exist on the device. Use farmbot_list_sequences to find available sequence IDs. This command blocks until the sequence completes or times out.
AI agents invoke farmbot_run_sequence 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.
farmbot_run_sequence triggers execution of pre-defined hardware operations on a physical robotic device (FarmBot). While the sequences themselves are saved and pre-approved, executing them has real-world effects on the garden hardware—moving the gantry, controlling water, actuating tools, etc.
From the tool's definition Execute a saved sequence on the FarmBot device via MQTT. This command blocks until the sequence completes or times out.
Attacks that exploit this kind of access
Execute a saved sequence on the FarmBot device via MQTT. Runs the sequence identified by ID. The sequence must already exist on the device. Use farmbot_list_sequences to find available sequence IDs. This command blocks until the sequence completes or times out. 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.
Register the Farmbot Agent MCP server in PolicyLayer and add a rule for farmbot_run_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 Farmbot Agent. Nothing to install.
farmbot_run_sequence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the farmbot_run_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.
Set action: deny in the PolicyLayer policy for farmbot_run_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.
farmbot_run_sequence 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 →