Register a sensor on a GPIO pin (e.g. soil moisture probe). Use farmbot_read_pin to read; readings are stored as sensor_readings (see farmbot_list_sensor_readings).
AI agents use farmbot_add_sensor 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 sensor configuration on the FarmBot hardware. While it is reversible (the sensor registration can be deleted or modified), it modifies the device's hardware configuration state. It does not retrieve data (Read), execute arbitrary code (Execute), permanently destroy data (Destructive), or move money (Financial).
From the tool's definition Register a sensor on a GPIO pin (e.g. soil moisture probe)—'register' indicates creation of a new configuration object in the hardware setup; this creates a persistent device mapping that can be modified or removed later.
Attacks that exploit this kind of access
Register a sensor on a GPIO pin (e.g. soil moisture probe). Use farmbot_read_pin to read; readings are stored as sensor_readings (see farmbot_list_sensor_readings). 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_sensor: 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_sensor 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_sensor 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_sensor. 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_sensor 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 →