ai_suggest_progressive_overload
AI-powered progressive overload suggestions. Analyzes recent workout history and suggests weight/rep/set increases for the next session.
This record as markdown: /tools/app-businys-mcp-server/ai-suggest-progressive-overload.md
What ai_suggest_progressive_overload does on Businys
AI agents call ai_suggest_progressive_overload to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ai_suggest_progressive_overload is rated Low
The tool performs analysis of historical workout data and returns recommendations (suggestions) for the next session. It does not modify, create, or delete any records. This is a read/query operation with an AI inference layer on top. Severity is low because misuse would at worst produce incorrect fitness advice, with no data integrity or financial risk.
From the tool's definition 'Analyzes recent workout history and suggests weight/rep/set increases' — the tool reads/analyzes existing data and produces suggestions, with no indication of writing or executing changes.
Attacks that exploit this kind of access
The rule that runs ai_suggest_progressive_overload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ai_suggest_progressive_overload, this is the rule to start with:
ai_suggest_progressive_overload 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 Businys, apply this rule, and every ai_suggest_progressive_overload call is checked against it from then on.
Questions about ai_suggest_progressive_overload
AI-powered progressive overload suggestions. Analyzes recent workout history and suggests weight/rep/set increases for the next session. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for ai_suggest_progressive_overload: 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 Businys. Nothing to install.
ai_suggest_progressive_overload 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 ai_suggest_progressive_overload 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 ai_suggest_progressive_overload. 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.
ai_suggest_progressive_overload is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue