bmr_calculator
Basal metabolic rate (Mifflin–St Jeor) and daily calories (TDEE = BMR × activity). Runs on smart-tools.xyz.
This record as markdown: /tools/io-github-9thshini-smart-tools/bmr-calculator.md
What bmr_calculator does on SmartTools
AI agents invoke bmr_calculator to trigger actions in SmartTools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
age | number | string | Yes | Age in years |
sex | string | Yes | Biological sex |
locale | string | — | Language for the source_url link (default en) |
activity | number | string | — | Activity multiplier: 1.2 sedentary, 1.375 light, 1.55 moderate, 1.725 active, 1.9 very active (default 1.2) |
height_cm | number | string | Yes | Height in cm |
weight_kg | number | string | Yes | Weight in kg |
Parameters from the server's own tool schema.
Why bmr_calculator is rated High
bmr_calculator triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs bmr_calculator safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bmr_calculator, this is the rule to start with:
bmr_calculator stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartTools, apply this rule, and every bmr_calculator call is checked against it from then on.
Questions about bmr_calculator
Basal metabolic rate (Mifflin–St Jeor) and daily calories (TDEE = BMR × activity). Runs on smart-tools.xyz. It is categorised as a Execute tool in the SmartTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
bmr_calculator accepts 6 parameters: age, sex, locale, activity, height_cm, weight_kg. Required: age, sex, height_cm, weight_kg. The full parameter table on this page comes from the server's own tool schema.
Register the SmartTools MCP server in PolicyLayer and add a rule for bmr_calculator: 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 SmartTools. Nothing to install.
bmr_calculator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bmr_calculator 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 bmr_calculator. 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.
bmr_calculator is provided by the SmartTools MCP server (https://smart-tools.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartTools, and thousands of servers like it.
Across the catalogue