treasury_tic_holder_history

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/treasury-tic-holder-history.md

WHAT IT DOES

What treasury_tic_holder_history does on Livedatalink

AI agents use treasury_tic_holder_history to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.

Parameter	Type	Required	Description
`limit`	integer	—	Maximum observations. Default 24.
`holder`	string	Yes	Exact MFH holder id or unambiguous published label. Use treasury_tic_find_holders first if unsure.
`offset`	integer	—	Observations to skip. Default 0.
`end_month`	string	—	Exact calendar month in YYYY-MM format.
`start_month`	string	—	Exact calendar month in YYYY-MM format.
`response_format`	string	—	Human-readable markdown or machine-readable JSON. Default markdown.
`include_comparison_series`	boolean	—	Include separately preserved prior-series comparison values at historical breaks. Default false.

Parameters from the server's own tool schema.

RISK

Why treasury_tic_holder_history is rated Medium

An AI agent can call treasury_tic_holder_history faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs treasury_tic_holder_history 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_tic_holder_history, this is the rule to start with:

treasury_tic_holder_history Rate-limited

treasury_tic_holder_history stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "treasury_tic_holder_history": {
      "limits": [
        {
          "counter": "treasury_tic_holder_history_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every treasury_tic_holder_history call is checked against it from then on.

FAQ

Questions about treasury_tic_holder_history

What does the treasury_tic_holder_history tool do? +

How did one publisher-listed major foreign holder's U.S. Treasury holdings change over a fixed monthly window? Returns bounded/paginated holdings in integer USD millions, exact month, primary/comparison-series identity, raw-asset line references, snapshot vintage, hashes, and methodology caveats. Primary values are returned by default; set include_comparison_series only to inspect duplicate benchmark-break comparison columns. It is categorised as a Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does treasury_tic_holder_history accept? +

treasury_tic_holder_history accepts 7 parameters: limit, holder, offset, end_month, start_month, response_format, include_comparison_series. Required: holder. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on treasury_tic_holder_history? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for treasury_tic_holder_history: 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.

What risk level is treasury_tic_holder_history? +

treasury_tic_holder_history is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit treasury_tic_holder_history? +

Yes. Add a rate_limit block to the treasury_tic_holder_history 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.

How do I block treasury_tic_holder_history completely? +

Set action: deny in the PolicyLayer policy for treasury_tic_holder_history. 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.

What MCP server provides treasury_tic_holder_history? +

treasury_tic_holder_history 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.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →