tdee
Calorie Needs (BMR + TDEE) — Daily calorie needs: Mifflin–St Jeor basal metabolic rate, total daily energy expenditure by activity level, and a cut/maintain/bulk goal table.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/tdee.md
What tdee does on Gateway
AI agents call tdee 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 |
|---|---|---|---|
age | integer | Yes | Age in years |
sex | string | — | 'male' or 'female' (default male) |
activity | string | — | sedentary | light | moderate | active | very_active (default moderate) |
height_cm | number | Yes | Height in centimetres |
weight_kg | number | Yes | Body weight in kilograms |
Parameters from the server's own tool schema.
Why tdee is rated Low
This is a purely computational tool that performs health/fitness calculations and returns results. It reads input parameters and outputs calculated values without creating, modifying, deleting, or executing external operations. No financial transactions, data destruction, or side effects occur. The blast radius of misuse is minimal—incorrect calorie calculations affect only the user's personal fitness planning.
From the tool's definition Tool computes and returns calorie needs calculations (BMR, TDEE) based on user inputs. Description uses verbs like 'Daily calorie needs' and 'a cut/maintain/bulk goal table' indicating data retrieval/calculation output with no modification of external state…
Attacks that exploit this kind of access
The rule that runs tdee 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 tdee, this is the rule to start with:
tdee 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 tdee call is checked against it from then on.
Questions about tdee
Calorie Needs (BMR + TDEE) — Daily calorie needs: Mifflin–St Jeor basal metabolic rate, total daily energy expenditure by activity level, and a cut/maintain/bulk goal table. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
tdee accepts 5 parameters: age, sex, activity, height_cm, weight_kg. Required: age, height_cm, weight_kg. 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 tdee: 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.
tdee 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 tdee 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 tdee. 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.
tdee 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