Get information about specific equipment.
AI agents call get_equipment_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 queries and retrieves equipment data from the farm management system. There is no evidence of write, delete, execute, or financial operations. It is purely informational, consistent with other sibling read-only tools (get_farm_info, get_field_info, list_equipment_by_farm). The blast radius of misuse is minimal—an agent could only access existing equipment records.
From the tool's definition Tool name 'get_equipment_info' and description 'Get information about specific equipment' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get information about specific equipment. 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_equipment_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_equipment_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_equipment_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_equipment_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_equipment_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 →