Sync the FarmBot device with the web application. Triggers the device to download the latest data from the FarmBot web app, including sequences, farm events, and device settings. Run this after making changes via the REST API to ensure the device has the latest configuration.
AI agents invoke farmbot_sync 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.
While sync itself is not destructive or financial, it executes a device operation with effects that depend on the state of the web application and prior API changes. The tool initiates hardware-level synchronization which could propagate configuration changes to physical gardening equipment. This falls under Execute rather than Read because it actively triggers a device operation, not merely queries state.
From the tool's definition Tool description states it "Triggers the device to download the latest data" and must be run "after making changes via the REST API to ensure the device has the latest configuration." The verb 'Triggers' indicates an external operation that causes the device…
Attacks that exploit this kind of access
Sync the FarmBot device with the web application. Triggers the device to download the latest data from the FarmBot web app, including sequences, farm events, and device settings. Run this after making changes via the REST API to ensure the device has the latest configuration. 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_sync: 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_sync 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_sync 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_sync. 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_sync 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 →