calculateCaloriesBurned
Calculates calories burned from an activity, weight in pounds, and duration in minutes. Requires an activity, which matches activity names, common synonyms, and fitness-platform workout type identifiers (e.g. HKWorkoutActivityTypeElliptical, EXERCISE_TYPE_PILATES); up to 10 matches are returned, ...
This record as markdown: /tools/com-api-ninjas-mcp/calculatecaloriesburned.md
What calculateCaloriesBurned does on API Ninjas
AI agents call calculateCaloriesBurned 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 |
|---|---|---|---|
age | integer | — | Age of the user in years. Must be between 13 and 120. To personalize the estimate, provide age, sex, and height together (or rmr instead). |
rmr | integer | — | Resting metabolic rate of the user in calories per day, if known. Must be between 500 and 5000. When provided, it is used instead of age, sex, and height. |
sex | string | — | Sex of the user. Use together with age and height. |
height | number | — | Height of the user in inches. Must be between 36 and 96. Use together with age and sex. |
weight | integer | — | Weight of the user performing the activity in pounds. Must be between 50 and 500. Default value is 160. |
activity | string | Yes | Name of the activity. Accepts activity names, common synonyms, and fitness-platform workout type identifiers. This value can be partial. |
duration | integer | — | How long the activity was performed in minutes. Must be 1 or greater. Default value is 60 (1 hour). |
Parameters from the server's own tool schema.
Why calculateCaloriesBurned is rated Low
Even though calculateCaloriesBurned 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 calculateCaloriesBurned 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 calculateCaloriesBurned, this is the rule to start with:
calculateCaloriesBurned 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 calculateCaloriesBurned call is checked against it from then on.
Questions about calculateCaloriesBurned
Calculates calories burned from an activity, weight in pounds, and duration in minutes. Requires an activity, which matches activity names, common synonyms, and fitness-platform workout type identifiers (e.g. HKWorkoutActivityTypeElliptical, EXERCISE_TYPE_PILATES); up to 10 matches are returned, best match first. For all names use /caloriesburnedactivities. Optionally personalize with age, sex, and height together, or rmr (resting metabolic rate). Photorealistic image_url and transparent icon_url fields are returned only for paid subscriptions, for activities that have an image. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
calculateCaloriesBurned accepts 7 parameters: age, rmr, sex, height, weight, activity, duration. Required: activity. 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 calculateCaloriesBurned: 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.
calculateCaloriesBurned 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 calculateCaloriesBurned 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 calculateCaloriesBurned. 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.
calculateCaloriesBurned 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