one_rep_max
One-Rep Max (1RM) Estimator — Estimate one-rep max from a weight x reps set (Epley + Brzycki) plus a percentage-of-1RM training table with load and rep targets.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/one-rep-max.md
What one_rep_max does on Gateway
AI agents call one_rep_max 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 |
|---|---|---|---|
reps | integer | Yes | Reps performed at that weight |
unit | string | — | Weight unit label, e.g. 'lb' or 'kg' (default 'lb') |
weight | number | Yes | Weight lifted |
Parameters from the server's own tool schema.
Why one_rep_max is rated Low
This tool purely performs a mathematical calculation/estimation based on input values (weight and reps) and returns computed results. It has no side effects, does not write or delete data, and involves no financial operations. It is a read/compute-only fitness calculator.
From the tool's definition Estimate one-rep max from a weight x reps set (Epley + Brzycki) plus a percentage-of-1RM training table with load and rep targets
Attacks that exploit this kind of access
The rule that runs one_rep_max 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 one_rep_max, this is the rule to start with:
one_rep_max 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 one_rep_max call is checked against it from then on.
Questions about one_rep_max
One-Rep Max (1RM) Estimator — Estimate one-rep max from a weight x reps set (Epley + Brzycki) plus a percentage-of-1RM training table with load and rep targets. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
one_rep_max accepts 3 parameters: reps, unit, weight. Required: reps, weight. 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 one_rep_max: 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.
one_rep_max 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 one_rep_max 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 one_rep_max. 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.
one_rep_max 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