lmpr.lamb.carcass_cutout
National estimated lamb carcass cutout value (LM_XL502). Returns gross carcass value, foresaddle value (rib, shoulder, breast/neck), hindsaddle value (leg, loin), net carcass value, and other byproduct values (pelt, offal). Published daily on USDA business days. Source: USDA LMPR Datamart, US Gov...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/lmpr.lamb.carcass-cutout.md
What lmpr.lamb.carcass_cutout does on Apibase
AI agents call lmpr.lamb.carcass_cutout 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.lamb.carcass_cutout is rated Low
Retrieves public USDA livestock market pricing data without side effects.
From the tool's definition Returns estimated lamb carcass cutout value, published daily by USDA.
Attacks that exploit this kind of access
The rule that runs lmpr.lamb.carcass_cutout 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.lamb.carcass_cutout, this is the rule to start with:
lmpr.lamb.carcass_cutout 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.lamb.carcass_cutout call is checked against it from then on.
Questions about lmpr.lamb.carcass_cutout
National estimated lamb carcass cutout value (LM_XL502). Returns gross carcass value, foresaddle value (rib, shoulder, breast/neck), hindsaddle value (leg, loin), net carcass value, and other byproduct values (pelt, offal). Published daily on USDA business days. Source: USDA LMPR 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.lamb.carcass_cutout 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.lamb.carcass_cutout: 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.lamb.carcass_cutout 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.lamb.carcass_cutout 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.lamb.carcass_cutout. 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.lamb.carcass_cutout 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