Find the home position using encoders or endstops. Moves the specified axis (or all axes) until it hits an endstop or stall-detection triggers, then sets that position as 0. This is more thorough than farmbot_home which simply moves to the stored 0 position.
AI agents invoke farmbot_find_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 physically moves FarmBot hardware and modifies the stored home position (sets position as 0). It triggers external hardware operations with real-world effects on a physical device. While it writes a new zero position, its primary action is executing physical gantry movement and position calibration, making Execute the most accurate category.
From the tool's definition Moves the specified axis (or all axes) until it hits an endstop or stall-detection triggers, then sets that position as 0
Attacks that exploit this kind of access
Find the home position using encoders or endstops. Moves the specified axis (or all axes) until it hits an endstop or stall-detection triggers, then sets that position as 0. This is more thorough than farmbot_home which simply moves to the stored 0 position. 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_find_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_find_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_find_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_find_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_find_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 →