Get information about specific livestock.
AI agents call get_livestock_info to retrieve information from Farm OS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves livestock data without modifying, deleting, or executing operations. It is consistent with sibling tools (get_equipment_info, get_farm_info, get_sensor_readings) that are all read operations. There is no financial impact, no code execution, and no destructive capability.
From the tool's definition Tool name 'get_livestock_info' and description 'Get information about specific livestock' indicate a retrieval operation with no side effects. The verb 'Get' and context within a farm management system focused on 'monitoring' confirm this is a read-only query.
Attacks that exploit this kind of access
Get information about specific livestock. It is categorised as a Read tool in the Farm OS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Farm OS MCP Server MCP server in PolicyLayer and add a rule for get_livestock_info: 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 Farm OS MCP Server. Nothing to install.
get_livestock_info 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 get_livestock_info 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 get_livestock_info. 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.
get_livestock_info is provided by the Farm OS MCP Server MCP server (ramprasadchauhan/fast-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 →