Get a single regimen by ID, including its regimen_items (the actual schedule).
AI agents call farmbot_get_regimen to retrieve information from Farmbot Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries regimen schedule data from FarmBot by ID. It performs no side effects, data modification, code execution, or destructive operations. The verb 'Get' and lack of any write/execute capability confirms this is a read-only operation with minimal security risk.
From the tool's definition Tool name 'farmbot_get_regimen' and description 'Get a single regimen by ID, including its regimen_items' clearly indicate a retrieval operation with no modification of state.
Attacks that exploit this kind of access
Get a single regimen by ID, including its regimen_items (the actual schedule). It is categorised as a Read tool in the Farmbot Agent MCP Server, which means it retrieves data without modifying state.
Register the Farmbot Agent MCP server in PolicyLayer and add a rule for farmbot_get_regimen: 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_get_regimen is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the farmbot_get_regimen 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_get_regimen. 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_get_regimen 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 →