sec_ftd_compare
Compare two to eight ticker symbols on the same SEC fails-to-deliver settlement date from the self-hosted official snapshot. Returns published quantities, explicit missing-row status, issuer labels, ranking, coverage, and provenance; a missing row is never converted to zero. Use this for 'compare...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/sec-ftd-compare.md
What sec_ftd_compare does on Livedatalink
AI agents call sec_ftd_compare 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 |
|---|---|---|---|
symbols | array | Yes | Two to eight unique exact ticker symbols. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
settlement_date | string | — | Settlement date in YYYY-MM-DD format, within the hosted hot window. |
Parameters from the server's own tool schema.
Why sec_ftd_compare is rated Low
Even though sec_ftd_compare 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.
Attacks that exploit this kind of access
The rule that runs sec_ftd_compare 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 sec_ftd_compare, this is the rule to start with:
sec_ftd_compare 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 sec_ftd_compare call is checked against it from then on.
Questions about sec_ftd_compare
Compare two to eight ticker symbols on the same SEC fails-to-deliver settlement date from the self-hosted official snapshot. Returns published quantities, explicit missing-row status, issuer labels, ranking, coverage, and provenance; a missing row is never converted to zero. Use this for 'compare GME, AMC, and TSLA FTD balances' or 'which selected symbol had the largest published balance on 2026-08-14?'. Point-in-time balances are not daily flows, wrongdoing evidence, or investment advice. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
sec_ftd_compare accepts 3 parameters: symbols, response_format, settlement_date. Required: symbols. 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 sec_ftd_compare: 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.
sec_ftd_compare 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 sec_ftd_compare 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 sec_ftd_compare. 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.
sec_ftd_compare 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