lmpr.cattle.slaughter_prices
5-Area daily weighted-average direct slaughter cattle prices (LM_CT100). Returns head counts, price ranges ($/cwt), and weighted averages by class (steer/heifer) and selling basis (live FOB, dressed delivered, dressed FOB). Covers TX/OK/NM, Kansas, Nebraska, Colorado, and Iowa/Minnesota feedlot r...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/lmpr.cattle.slaughter-prices.md
What lmpr.cattle.slaughter_prices does on Apibase
AI agents call lmpr.cattle.slaughter_prices to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
report_date | string | — | Report date in YYYY-MM-DD or M/D/YYYY format (e.g. "2026-06-27"). Omit for the most recent published report. |
all_sections | boolean | — | Return all report sections (price detail, primal values, etc.). Default true. Set false for summary only. |
Parameters from the server's own tool schema.
Why lmpr.cattle.slaughter_prices is rated Low
Retrieves published livestock market data with no ability to modify, delete, or execute operations.
From the tool's definition Returns head counts, price ranges, weighted averages; queries USDA public data.
Attacks that exploit this kind of access
The rule that runs lmpr.cattle.slaughter_prices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lmpr.cattle.slaughter_prices, this is the rule to start with:
lmpr.cattle.slaughter_prices is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every lmpr.cattle.slaughter_prices call is checked against it from then on.
Questions about lmpr.cattle.slaughter_prices
5-Area daily weighted-average direct slaughter cattle prices (LM_CT100). Returns head counts, price ranges ($/cwt), and weighted averages by class (steer/heifer) and selling basis (live FOB, dressed delivered, dressed FOB). Covers TX/OK/NM, Kansas, Nebraska, Colorado, and Iowa/Minnesota feedlot regions combined. Published daily on USDA business days. Source: USDA Livestock Mandatory Price Reporting Datamart, US Government public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
lmpr.cattle.slaughter_prices accepts 2 parameters: report_date, all_sections. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for lmpr.cattle.slaughter_prices: 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 Apibase. Nothing to install.
lmpr.cattle.slaughter_prices 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 lmpr.cattle.slaughter_prices 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 lmpr.cattle.slaughter_prices. 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.
lmpr.cattle.slaughter_prices is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue