usdamars.reports.corrected
List USDA AMS market news reports that have been corrected or amended within the specified period. Corrections supersede previously published data and are important for accurate commodity price analysis. Covers livestock, dairy, poultry, produce, grain, and cotton markets. Use days=all to see the...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/usdamars.reports.corrected.md
What usdamars.reports.corrected does on Apibase
AI agents call usdamars.reports.corrected 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 |
|---|---|---|---|
days | string | number | — | Number of past days to search for corrections (1–90), or "all" for complete history. Default "all". |
Parameters from the server's own tool schema.
Why usdamars.reports.corrected is rated Low
Tool retrieves and queries publicly available USDA commodity market correction data with no side effects.
From the tool's definition List USDA AMS market news reports that have been corrected within specified period.
Attacks that exploit this kind of access
The rule that runs usdamars.reports.corrected 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 usdamars.reports.corrected, this is the rule to start with:
usdamars.reports.corrected 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 usdamars.reports.corrected call is checked against it from then on.
Questions about usdamars.reports.corrected
List USDA AMS market news reports that have been corrected or amended within the specified period. Corrections supersede previously published data and are important for accurate commodity price analysis. Covers livestock, dairy, poultry, produce, grain, and cotton markets. Use days=all to see the full correction history. Source: USDA AMS MyMarketNews — marsapi.ams.usda.gov, public domain, no auth. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
usdamars.reports.corrected accepts 1 parameter: days. 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 usdamars.reports.corrected: 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.
usdamars.reports.corrected 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 usdamars.reports.corrected 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 usdamars.reports.corrected. 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.
usdamars.reports.corrected 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