getExecutiveCompensation
Returns named-executive-officer compensation for a company, sourced from SEC DEF 14A proxy statements, plus the structured Pay Versus Performance disclosure. The free tier returns the CEO's total for the latest fiscal year; premium tiers unlock the full breakdown, all executives, historical years...
This record as markdown: /tools/com-api-ninjas-mcp/getexecutivecompensation.md
What getExecutiveCompensation does on API Ninjas
AI agents call getExecutiveCompensation 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 | — | The company's SEC Central Index Key (CIK), with or without leading zeros (e.g., 320193 or 0000320193). An alternative to ticker. |
name | string | — | Company name to search for (e.g., apple), used when a ticker or cik is not provided. |
year | integer | — | The 4-digit fiscal year to return. Each response covers a single year and defaults to the latest available year. Historical (non-latest) years require a paid (p |
ticker | string | — | The stock ticker of the company (e.g., AAPL). Either ticker or name is required. |
Parameters from the server's own tool schema.
Why getExecutiveCompensation is rated Low
Even though getExecutiveCompensation 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 getExecutiveCompensation 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 getExecutiveCompensation, this is the rule to start with:
getExecutiveCompensation 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 getExecutiveCompensation call is checked against it from then on.
Questions about getExecutiveCompensation
Returns named-executive-officer compensation for a company, sourced from SEC DEF 14A proxy statements, plus the structured Pay Versus Performance disclosure. The free tier returns the CEO's total for the latest fiscal year; premium tiers unlock the full breakdown, all executives, historical years, and Pay Versus Performance. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getExecutiveCompensation accepts 4 parameters: cik, name, year, 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 getExecutiveCompensation: 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.
getExecutiveCompensation 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 getExecutiveCompensation 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 getExecutiveCompensation. 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.
getExecutiveCompensation 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