body_fat
Body-Fat Percentage (U.S. Navy) — Body-fat % via the U.S. Navy circumference method (height/neck/waist, plus hip for women), the ACE category, and fat/lean mass if a body weight is given.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/body-fat.md
What body_fat does on Gateway
AI agents call body_fat 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 |
|---|---|---|---|
sex | string | — | 'male' or 'female' (default male) |
hip_cm | number | — | Hip circumference in cm (required for the female estimate) |
neck_cm | number | Yes | Neck circumference in centimetres |
waist_cm | number | Yes | Waist circumference in centimetres |
height_cm | number | Yes | Height in centimetres |
weight_kg | number | — | Body weight in kg (optional; enables fat/lean mass) |
Parameters from the server's own tool schema.
Why body_fat is rated Low
This is a pure computational/query tool that retrieves a calculated result (body-fat percentage) from anthropometric inputs. It has no side effects, does not modify any data, and poses no security risk even if an AI agent misuses it with arbitrary inputs.
From the tool's definition Tool performs a calculation based on input measurements (height, neck, waist, hip) and returns body-fat percentage and ACE category—no state modification, data creation, deletion, code execution, or financial transaction.
Attacks that exploit this kind of access
The rule that runs body_fat 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 body_fat, this is the rule to start with:
body_fat 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 body_fat call is checked against it from then on.
Questions about body_fat
Body-Fat Percentage (U.S. Navy) — Body-fat % via the U.S. Navy circumference method (height/neck/waist, plus hip for women), the ACE category, and fat/lean mass if a body weight is given. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
body_fat accepts 6 parameters: sex, hip_cm, neck_cm, waist_cm, height_cm, weight_kg. Required: neck_cm, waist_cm, height_cm. 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 body_fat: 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.
body_fat 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 body_fat 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 body_fat. 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.
body_fat 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