getFailsToDeliver
Shares that did not settle on the contractual settlement date, published semi-monthly by the SEC. Persistent, large fails are the closest public signal to naked shorting. A security is listed only on dates it had a settlement failure, so an absent date means no material fails rather than no data.
This record as markdown: /tools/com-api-ninjas-mcp/getfailstodeliver.md
What getFailsToDeliver does on API Ninjas
AI agents call getFailsToDeliver to retrieve information from API Ninjas 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 | — | Number of records to return, 1 to 250. Defaults to 30. The free tier is limited to the latest record. |
ticker | string | Yes | The stock or ETF ticker symbol (e.g., GME). |
Parameters from the server's own tool schema.
Why getFailsToDeliver is rated Low
Even though getFailsToDeliver 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 getFailsToDeliver safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getFailsToDeliver, this is the rule to start with:
getFailsToDeliver 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 API Ninjas, apply this rule, and every getFailsToDeliver call is checked against it from then on.
Questions about getFailsToDeliver
Shares that did not settle on the contractual settlement date, published semi-monthly by the SEC. Persistent, large fails are the closest public signal to naked shorting. A security is listed only on dates it had a settlement failure, so an absent date means no material fails rather than no data. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getFailsToDeliver accepts 2 parameters: limit, ticker. Required: ticker. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getFailsToDeliver: 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 API Ninjas. Nothing to install.
getFailsToDeliver 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 getFailsToDeliver 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 getFailsToDeliver. 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.
getFailsToDeliver is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue