getInsiderTransactions

Returns a list of insider trading transactions that match the specified filters. Returns at most 100 results per request. For more results, use the offset parameter.

SERVERAPI Ninjas SOURCEhttps://mcp.api-ninjas.com/mcp

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-api-ninjas-mcp/getinsidertransactions.md

WHAT IT DOES

What getInsiderTransactions does on API Ninjas

AI agents call getInsiderTransactions 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	—	Central Index Key (CIK) of the company.
`name`	string	—	Name of the insider (exact match). Use /v1/insiderslist to look up insider names.
`limit`	integer	—	Maximum number of results to return (1-100, default: 25). Premium subscriptions only.
`offset`	integer	—	Number of results to skip for pagination (default: 0). Premium subscriptions only.
`ticker`	string	—	Company ticker symbol (e.g., AAPL, MSFT).
`form_type`	string	—	SEC form type (3, 4, or 5).
`insider_type`	string	—	Type of insider: 'director' (matches director or chairman), '10_percent_owner' (matches 10% Owner), or 'officer' (excludes director, 10% owner, and chairman).
`transaction_code`	string	—	Transaction code (e.g., P, S, A, D, F, etc.).
`transaction_date`	string	—	Transaction date in YYYY-MM-DD format.
`transaction_type`	string	—	Type of transaction (e.g., Purchase, Sale, Award, etc.).
`max_transaction_date`	string	—	Maximum transaction date in YYYY-MM-DD format.
`min_transaction_date`	string	—	Minimum transaction date in YYYY-MM-DD format.

Parameters from the server's own tool schema.

RISK

Why getInsiderTransactions is rated Low

Even though getInsiderTransactions 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.

Risk signalsHigh parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getInsiderTransactions 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 getInsiderTransactions, this is the rule to start with:

getInsiderTransactions Allowed

getInsiderTransactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getInsiderTransactions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API Ninjas, apply this rule, and every getInsiderTransactions call is checked against it from then on.

FAQ

Questions about getInsiderTransactions

What does the getInsiderTransactions tool do? +

Returns a list of insider trading transactions that match the specified filters. Returns at most 100 results per request. For more results, use the offset parameter. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.

What parameters does getInsiderTransactions accept? +

getInsiderTransactions accepts 12 parameters: cik, name, limit, offset, ticker, form_type, insider_type, transaction_code, transaction_date, transaction_type, max_transaction_date, min_transaction_date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getInsiderTransactions? +

Register the API Ninjas MCP server in PolicyLayer and add a rule for getInsiderTransactions: 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.

What risk level is getInsiderTransactions? +

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

Can I rate-limit getInsiderTransactions? +

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

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

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

KEEP EXPLORING

More on API Ninjas, and thousands of servers like it.

This server

All 244 API Ninjas tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →