treasury_auctions
Recent US Treasury securities auction results: term, CUSIP, issue/maturity dates, high yield, interest rate, bid-to-cover ratio, and amounts. Optionally filter by security type (Bill, Note, Bond, TIPS, FRN).
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/treasury-auctions.md
What treasury_auctions does on Livedatalink
AI agents call treasury_auctions to retrieve information from Livedatalink 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 | number | — | Max rows to return. |
security_type | string | — | Filter by security type: 'Bill', 'Note', 'Bond', 'TIPS', 'FRN'. |
Parameters from the server's own tool schema.
Why treasury_auctions is rated Low
This tool queries and retrieves publicly available financial data without creating, modifying, deleting, or executing any actions. It functions as a data lookup service for historical Treasury auction information. While the data relates to finance, the tool itself performs no financial transactions, commits no obligations, and has no side effects beyond returning read-only information.
From the tool's definition Tool retrieves historical Treasury auction results with no modification capability: 'Recent US Treasury securities auction results: term, CUSIP, issue/maturity dates, high yield, interest rate, bid-to-cover ratio, and amounts.' The description specifies only…
Attacks that exploit this kind of access
The rule that runs treasury_auctions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For treasury_auctions, this is the rule to start with:
treasury_auctions 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 Livedatalink, apply this rule, and every treasury_auctions call is checked against it from then on.
Questions about treasury_auctions
Recent US Treasury securities auction results: term, CUSIP, issue/maturity dates, high yield, interest rate, bid-to-cover ratio, and amounts. Optionally filter by security type (Bill, Note, Bond, TIPS, FRN). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
treasury_auctions accepts 2 parameters: limit, security_type. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for treasury_auctions: 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 Livedatalink. Nothing to install.
treasury_auctions 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 treasury_auctions 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 treasury_auctions. 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.
treasury_auctions is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue