getStockSplit
Returns historical and upcoming stock split records filtered by ticker, exchange, forward or reverse split type, and a single date or date range.
This record as markdown: /tools/com-api-ninjas-mcp/getstocksplit.md
What getStockSplit does on API Ninjas
AI agents call getStockSplit 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 |
|---|---|---|---|
date | string | — | Single date in YYYY-MM-DD format. Cannot be combined with date_start or date_end. |
limit | integer | — | Maximum results to return. Default 50, max 1000. |
offset | integer | — | Number of results to skip for pagination. Default 0. |
ticker | string | — | Company ticker symbol. For U.S.-listed stocks use the bare symbol (e.g. GOOG); for international listings include the exchange suffix as the symbol trades (e.g. |
date_end | string | — | Range end in YYYY-MM-DD format. |
exchange | string | — | Filter results to a single exchange by its code - for example US, JPX (Tokyo), LSE (London), HKSE (Hong Kong), or NSE (India). |
date_start | string | — | Range start in YYYY-MM-DD format. Free-tier users cannot query earlier than 24 months ago. |
split_type | string | — | Filter by split direction: forward (e.g. 4-for-1) or reverse (a consolidation, e.g. 1-for-10). |
Parameters from the server's own tool schema.
Why getStockSplit is rated Low
Even though getStockSplit 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 getStockSplit 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 getStockSplit, this is the rule to start with:
getStockSplit 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 getStockSplit call is checked against it from then on.
Questions about getStockSplit
Returns historical and upcoming stock split records filtered by ticker, exchange, forward or reverse split type, and a single date or date range. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getStockSplit accepts 8 parameters: date, limit, offset, ticker, date_end, exchange, date_start, split_type. 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 getStockSplit: 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.
getStockSplit 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 getStockSplit 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 getStockSplit. 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.
getStockSplit 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