usdamars.reports.get
Get metadata for a specific USDA AMS market news report by its numeric ID or slug (e.g. "nw_ls910"). Returns publication date, commodity period, report title, file type, and whether it is a correction or final report. Obtain report IDs from usdamars.reports.list or usdamars.reports.search. Source...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/usdamars.reports.get.md
What usdamars.reports.get does on Apibase
AI agents call usdamars.reports.get 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_id | string | number | Yes | USDA AMS MARS report ID or slug (e.g. 2826 or "nw_ls910"). Obtain IDs from usdamars.list_reports or usdamars.search_reports. |
Parameters from the server's own tool schema.
Why usdamars.reports.get is rated Low
Retrieves publicly available USDA market report metadata without side effects or data modification.
From the tool's definition Get metadata for a specific report by ID or slug. Returns publication date, commodity period, report title, file type.
Attacks that exploit this kind of access
The rule that runs usdamars.reports.get 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.get, this is the rule to start with:
usdamars.reports.get 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.get call is checked against it from then on.
Questions about usdamars.reports.get
Get metadata for a specific USDA AMS market news report by its numeric ID or slug (e.g. "nw_ls910"). Returns publication date, commodity period, report title, file type, and whether it is a correction or final report. Obtain report IDs from usdamars.reports.list or usdamars.reports.search. 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.get accepts 1 parameter: report_id. Required: report_id. 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.get: 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.get 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.get 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.get. 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.get 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