Set or update a farmware env var by key (upsert). Use this to override camera calibration values, weed detector thresholds, or any other on-device config. Always stored as a string.
AI agents use farmbot_set_farmware_env 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 modifies device configuration state reversibly without deleting data, placing it in the Write category. Severity is high because misconfiguring camera calibration or detector thresholds could cause the robotic gardening system to malfunction, damage plants, misidentify weeds, or behave unpredictably—representing significant operational risk, though not financial loss or permanent destruction.
From the tool's definition Tool description explicitly states 'Set or update a farmware env var by key (upsert)' and enables overriding critical device configurations like 'camera calibration values, weed detector thresholds, or any other on-device config.' The upsert operation creates…
Attacks that exploit this kind of access
Set or update a farmware env var by key (upsert). Use this to override camera calibration values, weed detector thresholds, or any other on-device config. Always stored as a string. 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_set_farmware_env: 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_set_farmware_env 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_set_farmware_env 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_set_farmware_env. 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_set_farmware_env 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 →