metabolic_age_calc
Compare BMR-based metabolic age to chronological age.
This record as markdown: /tools/io-github-scotia1973-bot-api-hub/metabolic-age-calc.md
What metabolic_age_calc does on GadgetHumans API Hub
AI agents call metabolic_age_calc to retrieve information from GadgetHumans API Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why metabolic_age_calc is rated Low
This is a purely computational utility that retrieves or calculates information (metabolic age metrics) and returns results. It has no capability to modify data, execute arbitrary code, trigger external operations, delete data, or handle financial transactions. The read-only nature and benign calculation scope place it firmly in the Read category with low severity.
From the tool's definition Tool performs a calculation-based comparison ('Compare BMR-based metabolic age to chronological age') with no side effects. Returns computed results based on input parameters without modifying, executing external operations, or affecting data systems.
Attacks that exploit this kind of access
The rule that runs metabolic_age_calc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GadgetHumans API Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For metabolic_age_calc, this is the rule to start with:
metabolic_age_calc 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 GadgetHumans API Hub, apply this rule, and every metabolic_age_calc call is checked against it from then on.
Questions about metabolic_age_calc
Compare BMR-based metabolic age to chronological age. It is categorised as a Read tool in the GadgetHumans API Hub MCP Server, which means it retrieves data without modifying state.
Register the GadgetHumans API Hub MCP server in PolicyLayer and add a rule for metabolic_age_calc: 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 GadgetHumans API Hub. Nothing to install.
metabolic_age_calc 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 metabolic_age_calc 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 metabolic_age_calc. 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.
metabolic_age_calc is provided by the GadgetHumans API Hub MCP server (pypi:gadgethumans-api-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GadgetHumans API Hub, and thousands of servers like it.
This server
Across the catalogue