List FarmBot device logs. Logs include status messages, toast notifications from Lua scripts, errors, and lifecycle events. Filter by type (info, success, warn, error, busy, fun, debug, assertion) and verbosity (0-3). Use this to follow a long-running Lua script or sequence — toast() messages app...
AI agents call farmbot_list_logs 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 existing log data with optional filtering by type and verbosity. It has no side effects on the FarmBot system, data, or hardware. It is a read-only monitoring/debugging tool suitable for following script execution progress. No destructive, write, execute, or financial operations are possible.
From the tool's definition Tool name includes 'list' and description states 'List FarmBot device logs' — a pure retrieval operation. Returns status messages, notifications, errors, and lifecycle events with no modification or deletion capability.
Attacks that exploit this kind of access
List FarmBot device logs. Logs include status messages, toast notifications from Lua scripts, errors, and lifecycle events. Filter by type (info, success, warn, error, busy, fun, debug, assertion) and verbosity (0-3). Use this to follow a long-running Lua script or sequence — toast() messages appear here. 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_list_logs: 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_list_logs 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_list_logs 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_list_logs. 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_list_logs 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 →