Move FarmBot to the home position (0, 0, 0) or home a specific axis. Homes using the device
AI agents invoke farmbot_home 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.
This tool triggers physical hardware movement on the FarmBot device, sending it to the home position. It executes an external operation (mechanical movement) whose effects depend on the current state of the hardware. It's not purely destructive, but it does actuate real-world machinery, which could cause collisions or damage if the device is in an unexpected state.
From the tool's definition Move FarmBot to the home position (0, 0, 0) or home a specific axis. Homes using the device
Attacks that exploit this kind of access
Move FarmBot to the home position (0, 0, 0) or home a specific axis. Homes using the device. 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_home: 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_home 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_home 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_home. 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_home 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 →