farmbot_update_point · Farmbot Agent MCP: Risk & Policy

WHAT IT DOES

What farmbot_update_point does on Farmbot Agent

AI agents use farmbot_update_point 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.

WHY IT NEEDS A POLICY

Why farmbot_update_point needs a policy

This tool modifies data (point coordinates, properties) but does not delete, execute arbitrary code, or trigger irreversible hardware actions. Updates are reversible via subsequent write operations. The medium severity reflects that corrupted point data could cause navigation or sensor placement errors in gardening operations, but damage is bounded and correctable.

From the tool's definition Tool name contains 'update' and description states 'Update any point (Weed, GenericPointer)' — modifies existing data records in the FarmBot system reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

farmbot_update_point Rate-limited

farmbot_update_point stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "farmbot_update_point": {
      "limits": [
        {
          "counter": "farmbot_update_point_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Farmbot Agent, so you can run agents against it safely.

FAQ

Questions about farmbot_update_point

What does the farmbot_update_point tool do? +

Update any point (Weed, GenericPointer) — for Plants prefer farmbot_update_plant which has a richer schema (plant_stage, planted_at). 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.

How do I enforce a policy on farmbot_update_point? +

Register the Farmbot Agent MCP server in PolicyLayer and add a rule for farmbot_update_point: 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.

What risk level is farmbot_update_point? +

farmbot_update_point is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit farmbot_update_point? +

Yes. Add a rate_limit block to the farmbot_update_point 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.

How do I block farmbot_update_point completely? +

Set action: deny in the PolicyLayer policy for farmbot_update_point. 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.

What MCP server provides farmbot_update_point? +

farmbot_update_point 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.