getAnalytics

Returns usage analytics and API call history for your own account, including which APIs you call most. Requires api_key as a query parameter. Calls here do not consume quota.

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

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

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

WHAT IT DOES

What getAnalytics does on API Ninjas

AI agents call getAnalytics 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
`api_key`	string	Yes	Your API Key. This is passed as a query parameter instead of in the header for this endpoint.

Parameters from the server's own tool schema.

RISK

Why getAnalytics is rated Low

Even though getAnalytics 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 signalsHandles credentials or secrets (api_key)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

getAnalytics Allowed

getAnalytics 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": {
    "getAnalytics": {}
  }
}

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 getAnalytics call is checked against it from then on.

FAQ

Questions about getAnalytics

What does the getAnalytics tool do? +

Returns usage analytics and API call history for your own account, including which APIs you call most. Requires api_key as a query parameter. Calls here do not consume quota. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.

What parameters does getAnalytics accept? +

getAnalytics accepts 1 parameter: api_key. Required: api_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getAnalytics? +

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

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

Can I rate-limit getAnalytics? +

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

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

getAnalytics 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 →