calories_burned
Calories Burned (MET) — Calories burned for an activity from its MET value, body weight and duration, plus a comparison table of common activities at the same weight and time.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/calories-burned.md
What calories_burned does on Gateway
AI agents call calories_burned to retrieve information from Gateway 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 |
|---|---|---|---|
activity | string | Yes | walking | running | cycling | swimming | jump_rope | weightlifting | yoga | hiking | rowing | elliptical | basketball | soccer | tennis | ... |
weight_kg | number | Yes | Body weight in kilograms |
duration_min | number | Yes | Activity duration in minutes |
Parameters from the server's own tool schema.
Why calories_burned is rated Low
This is a stateless calculation/lookup tool that generates informational output without creating, modifying, deleting, or executing external operations. It belongs in the Read category with low severity since misuse would only produce incorrect fitness information.
From the tool's definition The tool retrieves calculated calorie burn data based on input parameters (MET value, body weight, duration) and returns a comparison table. No side effects, modifications, or external operations occur.
Attacks that exploit this kind of access
The rule that runs calories_burned safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calories_burned, this is the rule to start with:
calories_burned 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 Gateway, apply this rule, and every calories_burned call is checked against it from then on.
Questions about calories_burned
Calories Burned (MET) — Calories burned for an activity from its MET value, body weight and duration, plus a comparison table of common activities at the same weight and time. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
calories_burned accepts 3 parameters: activity, weight_kg, duration_min. Required: activity, weight_kg, duration_min. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for calories_burned: 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 Gateway. Nothing to install.
calories_burned 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 calories_burned 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 calories_burned. 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.
calories_burned is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue