New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

sec_ftd_history

Return a bounded, paginated history of published nonzero SEC fails-to-deliver balance records for one ticker in the self-hosted hot window. Includes settlement dates, quantities, SEC price fields, source-row counts, pagination, and provenance. Use this for 'show GME FTD balances over time', 'char...

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 61 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/sec-ftd-history.md

What sec_ftd_history does on Livedatalink

AI agents call sec_ftd_history 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.

ParameterTypeRequiredDescription
limit integer — Maximum published dates. Default 30.
offset integer — Published dates to skip. Default 0.
symbol string Yes Exact ticker symbol as published by the SEC. Use sec_ftd_search_securities for issuer-name searches.
end_date string — Settlement date in YYYY-MM-DD format, within the hosted hot window.
start_date string — Settlement date in YYYY-MM-DD format, within the hosted hot window.
response_format string — Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

Why sec_ftd_history is rated Low

Even though sec_ftd_history only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about sec_ftd_history

What does the sec_ftd_history tool do? +

Return a bounded, paginated history of published nonzero SEC fails-to-deliver balance records for one ticker in the self-hosted hot window. Includes settlement dates, quantities, SEC price fields, source-row counts, pagination, and provenance. Use this for 'show GME FTD balances over time', 'chart TSLA published fail balances this quarter', or to inspect point-in-time changes. Do not sum the observations as daily flow; omitted dates are not filled with inferred zeros. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does sec_ftd_history accept? +

sec_ftd_history accepts 6 parameters: limit, offset, symbol, end_date, start_date, response_format. Required: symbol. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sec_ftd_history? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for sec_ftd_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 sec_ftd_history? +

sec_ftd_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sec_ftd_history? +

Yes. Add a rate_limit block to the sec_ftd_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 sec_ftd_history completely? +

Set action: deny in the PolicyLayer policy for sec_ftd_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 sec_ftd_history? +

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

More on Livedatalink, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.