getCryptoTreasury
Crypto asset positions reported to the SEC in quarterly XBRL filings. Coverage is limited to SEC filers (holders listed only outside the US are not included), and each position is as of the filer's reported period end. With no parameters, returns the largest current positions ranked by dollar val...
This record as markdown: /tools/com-api-ninjas-mcp/getcryptotreasury.md
What getCryptoTreasury does on API Ninjas
AI agents call getCryptoTreasury 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 |
|---|---|---|---|
cik | string | — | SEC Central Index Key of the filer, with or without leading zeros. |
name | string | — | Case-insensitive substring match on the filer name. Requires a Business or Professional subscription. |
asset | string | — | Restrict to one crypto asset. UNKNOWN returns positions whose asset the filing did not state and which could not be identified. |
limit | integer | — | Maximum results to return. Capped by tier: 5 on Free, 50 on Developer, 250 on Business and Professional. |
offset | integer | — | Number of results to skip, for pagination. |
period | string | — | Reporting period end as YYYY-MM-DD, or 'latest'. Defaults to the most recent period. History depth is limited by subscription tier. |
ticker | string | — | Stock ticker of the filer, e.g. MSTR. Private filers have no ticker; use cik. |
entity_type | string | — | OPERATING is a company holding crypto on its balance sheet. ETP is an exchange-traded product whose holdings are the fund itself. PRIVATE is a filer with no lis |
include_unverified | boolean | — | Include positions whose unit count does not reconcile with the filer's own reported fair value. Excluded by default; when included they are reproduced exactly a |
Parameters from the server's own tool schema.
Why getCryptoTreasury is rated Low
Even though getCryptoTreasury 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 getCryptoTreasury 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 getCryptoTreasury, this is the rule to start with:
getCryptoTreasury 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 getCryptoTreasury call is checked against it from then on.
Questions about getCryptoTreasury
Crypto asset positions reported to the SEC in quarterly XBRL filings. Coverage is limited to SEC filers (holders listed only outside the US are not included), and each position is as of the filer's reported period end. With no parameters, returns the largest current positions ranked by dollar value. Positions whose unit count does not reconcile with the filer's own fair value are excluded unless include_unverified is set. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getCryptoTreasury accepts 9 parameters: cik, name, asset, limit, offset, period, ticker, entity_type, include_unverified. 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 getCryptoTreasury: 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.
getCryptoTreasury 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 getCryptoTreasury 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 getCryptoTreasury. 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.
getCryptoTreasury 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