Delete a sensor.
AI agents call farmbot_remove_sensor to permanently remove resources in Farmbot Agent — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes sensor data or configurations from the FarmBot system. Deletion operations are classified as Destructive rather than Write because they cannot be undone—removing a sensor eliminates its configuration and associated data permanently.
From the tool's definition Tool name is 'farmbot_remove_sensor' and description states 'Delete a sensor.' The verb 'Delete' combined with the irreversible nature of removing a physical sensor configuration indicates destructive intent.
Attacks that exploit this kind of access
Delete a sensor. It is categorised as a Destructive tool in the Farmbot Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Farmbot Agent MCP server in PolicyLayer and add a rule for farmbot_remove_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_remove_sensor is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the farmbot_remove_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_remove_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_remove_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 →