treasurydirect.auction.upcoming
Announced upcoming US Treasury security auctions not yet held. Returns the auction schedule including security type (Bill/Note/Bond), term, announcement date, auction date, and issue date for each forthcoming offering. Typically lists 1-2 weeks of upcoming auctions across all security types. Sour...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/treasurydirect.auction.upcoming.md
What treasurydirect.auction.upcoming does on Apibase
AI agents call treasurydirect.auction.upcoming 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 |
|---|---|---|---|
limit | integer | — | Maximum number of upcoming auction announcements to return (1–50). Announcements cover Bills, Notes, and Bonds typically scheduled 1–2 weeks ahead. |
Parameters from the server's own tool schema.
Why treasurydirect.auction.upcoming is rated Low
Retrieves public Treasury auction schedule information without modifying or executing operations.
From the tool's definition Returns auction schedule; no side effects. Public government data.
Attacks that exploit this kind of access
The rule that runs treasurydirect.auction.upcoming 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 treasurydirect.auction.upcoming, this is the rule to start with:
treasurydirect.auction.upcoming 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 treasurydirect.auction.upcoming call is checked against it from then on.
Questions about treasurydirect.auction.upcoming
Announced upcoming US Treasury security auctions not yet held. Returns the auction schedule including security type (Bill/Note/Bond), term, announcement date, auction date, and issue date for each forthcoming offering. Typically lists 1-2 weeks of upcoming auctions across all security types. Source: TreasuryDirect TA_WS, US Government open data, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
treasurydirect.auction.upcoming accepts 1 parameter: limit. 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 treasurydirect.auction.upcoming: 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.
treasurydirect.auction.upcoming 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 treasurydirect.auction.upcoming 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 treasurydirect.auction.upcoming. 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.
treasurydirect.auction.upcoming 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